Cloud Run

Cloud Run is where a bad deploy hurts most — a broken revision is serving live traffic right now. enoki gives you the two moves that matter in that moment: roll back to a known-good revision, and split traffic for a canary. Reads run under your identity; both traffic changes are approval-gated.

Reads

• list_cloud_run_services(project_id, region="us-central1") — services in a region, with their URL and status.
• list_cloud_run_revisions(service, region="us-central1", project_id) — the revisions of a service, so you can see exactly what you’re able to roll back to.

Writes — approval-gated

• rollback_cloud_run_service(service, revision, region="us-central1", project_id) — write. Sends 100% of traffic to one existing revision. The one-move fix when the latest rollout is bad.
• split_cloud_run_traffic(service, revision, percent, region="us-central1", project_id) — write. Sends percent (1–99) to the named revision and the remainder to the latest — a canary, or a graded rollback.

What a rollback actually changes

enoki only ever re-points traffic between revisions that already exist — it never builds, deploys, or deletes a revision. The plan you approve names the exact service, region, revision, and split; if anything about it changed between the proposal and your click, the approval is void and nothing happens. See Guardrails.

Next: Pub/Sub.