# One-command rollback

A step of the [Cloud application](https://gradus.kazet.blog/tree/cloud-application) tree on Gradus, in the Build & ship area: Config, lint, releases, IaC.

Page: https://gradus.kazet.blog/tree/cloud-application/step/rollback

Make undoing a release one command, and let a failed post-deploy check undo it by itself, so a bad release costs a minute rather than an evening.

Usually comes after: [First deploy](https://gradus.kazet.blog/tree/cloud-application/step/first-deploy).

Leads to: [Reversible migrations](https://gradus.kazet.blog/tree/cloud-application/step/reversible-migrations).

## Prompt for your AI assistant

```
Read the cloud provider decision record in docs/decisions. Tag every image this project deploys with its commit SHA, add a rollback workflow that puts the previous good version back on the public URL with one command and make the post-deploy health check run it when a new version fails. Then prove it: ship a release that fails /health on purpose, watch it roll back, write the command and the time it took into docs/runbooks/rollback.md and revert the change.
```

Every step of the tree: https://gradus.kazet.blog/tree/cloud-application/llms.txt