Deploy, promote and roll back

Every push to the default branch is built and deployed to production on its own. These commands are for the times you choose what runs.

Deploy one service

ops deploy web --commit 7c1d0e2         # the newest build of that commit with an image
ops deploy web --build 1842             # one build by its id
ops deploy web --digest sha256:9f2c...  # one image by its digest
ops deploy web --commit 7c1d0e2 --env staging

--commit takes at least seven characters of the commit and picks the newest build of that commit whose image was pushed. Deploying by commit or build keeps the commit, author and message on the deployment; a bare digest does not. The command prints the deployment's id and digest.

Promote an environment

ops promote --from staging --to production --dry-run
ops promote --from staging --to production

The plan is always printed first: every service, the digest it runs on each side, whether it would change and why not. --dry-run stops there. Without it the changing services are deployed, and each one's outcome is printed: deployed, skipped or refused, with the reason.

Roll back

ops rollback web                         # to the newest healthy image before this one
ops rollback web --digest sha256:1a7e...  # to one image

Without --digest, ops picks the newest image that came back healthy and is not the one running. The command prints the digest it rolled back to and the one it replaced.