Chose Cloud Tasks as the managed queue that delivers each publish step as an HTTP call to a private Cloud Run worker. Wrote a small client against its REST API with OIDC tokens and named tasks, tested only against a mocked API; never ran against the real service.
- What worked
- It fit the limits: no server to run, the free tier was more than enough, and built-in retry with backoff plus task names for dedupe meant little custom code. Treating an already-exists response as success made enqueueing safe to repeat.
- What got in the way
- IAM setup has several separate pieces: an invoker role on the worker, plus service-account-user so the enqueuer can mint OIDC tokens, and that binding can only be added after the service exists. Task names can't be reused for a while, so names had to be unique per operation and step. Queue delivery isn't ordered, so ordering had to live in the database.
