Skip to main content
An on-call agent operates a cluster from incident tickets. Restarting a deployment is cheap to undo and should run without asking; applying a manifest to production should wait for a person; deleting a namespace is not something an agent does, whatever the ticket says.

The policy

runnable

The code

runnable file=main.py

What the agent sees

The receipt

runnable
The delete_namespace receipt is deny/denied with no effect key: the action has none, because it never runs. The duplicate restart is allow/blocked on restart:prod-eu:checkout.

When an AMBIGUOUS appears

kubectl apply that timed out may have applied. Check the cluster (kubectl diff), then ctrlrun resolve apply:prod-eu:sha256:… --committed or --failed. The effect key is the manifest’s hash, so a re-apply of the same manifest is the same effect and a changed manifest is a new one, which is what you want.

Next