Rolling back

Rollback restores an environment to a previous known-good state when something goes wrong. It runs in two phases: create a rollback plan to review what will change, then apply it to execute the rollback.

---

What can be a rollback target

To serve as a rollback target, a release must have its deployment context stored in S3. That context holds the complete deployment state: stack version, overrides, resource metadata, modules, and resources, retrieved when you plan the rollback.

You also need release-authority permission. Deployments created before Facets began storing deployment context cannot be rollback targets; if you pick one, Facets prompts you to choose a more recent release instead.

---

Creating a rollback plan

Creating the plan changes nothing on the environment. It only previews the rollback.

1. Open the resource in Projects > Resources, select it, and go to its Release History tab.
2. On the release you want to roll back to, click Rollback. The rollback plan is scoped to that one resource. The button is hidden on APPLY_ROLLBACK_PLAN rows, and disabled when the old and new versions are identical.
3. The system generates a ROLLBACK_PLAN release type that shows what will change.
4. Review the plan. It compares your current state against the state you are reverting to, so you can verify the impact before proceeding: the resources that will be restored, the stack versions that will be applied, the configuration changes between current and previous state, and the Terraform changes that will execute.

---

Applying the rollback plan

The rollback only takes effect once you apply the plan.

1. Open the ROLLBACK_PLAN release from the environment's release history.
2. Review the planned changes one more time, in particular any resource the plan will destroy or replace.
3. Click Apply Plan and confirm.

Facets records the applied release as an APPLY ROLLBACK PLAN release, separate from the ROLLBACK_PLAN release that produced it. Both stay in the release history, so the plan you reviewed and the apply that acted on it remain auditable.

To verify the restored state:

• Confirm the APPLY ROLLBACK PLAN release finished with a SUCCEEDED status.
• Open the release and check the Terraform logs to confirm the changes the plan listed are the changes that ran.
• Check the environment's resources against the release you rolled back to.

If the environment has a release approval gate configured, the apply passes through it like any other release.