Overview
Every successful deploy records a release: the image tags that went live for each service, the git commit and branch they were built from, and a monotonically increasing release number. fjall releases lists that history; fjall rollback re-deploys a previous release’s exact images.
Listing Releases
Output:
▸ marks the release currently live; (rollback) marks releases that restored an earlier one.
Options
Rolling Back
A rollback re-registers each service’s task definition with the target release’s recorded image tags and rolls the services. It does not rebuild anything and does not touch your infrastructure — it moves the running code back to images that already exist in ECR.
The rollback itself is recorded as a new release pointing at the release it restored, so the history stays linear and auditable.
Options
Rolling back restores code, not data. If the release you are leaving ran
database migrations, verify the older code is compatible with the current
schema before rolling back.
fjall rollout — restart running services in place (for rotated secrets), no image changefjall deploy — build and deploy a new release
