liveBook · Manning

Rollback

As explained in Kargo in Action

A deployment operation that returns an environment to a previous artifact or application state.

Rollback returns a deployment to a known-good previous state. It depends on being able to identify that state; without a promotion record, a mutable tag may no longer point to the artifact it named earlier. section 1.1.2

A risky hotfix reversal

After a Friday hotfix, a team may need to reverse a production change. If it cannot identify the previously validated artifact, “the previous version” is only a guess about where a mutable tag pointed. section 1.1.2

How Kargo in Action covers it

How deep it goes
Explains the need for a promotion record and the risk of mutable tags, but gives no rollback procedure.
Examples
Uses a Friday production hotfix and a mutable tag to illustrate uncertainty about the prior state.
What you can do after
Understand why a promotion record is needed to identify a trustworthy rollback target.
How it connects
Connects rollback to promotion records, mutable tags, and hotfixes.

Also explained in

Compare how 14 books explain rollback →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Kargo in Action. The section links point to the parts of the book it draws on.