Rollback

As explained in Infrastructure as Code, Patterns and Practices: With examples in Python and Terraform

Rollback is the restoration of infrastructure configuration or system state to an earlier known-good version.

Rollback restores infrastructure configuration or system state to a known-good version. With infrastructure as code, immutability makes this a forward-moving undo rather than a full state restoration. section 11.1.1

Handle a failed infrastructure change by:

• Prioritize stabilization and restoration of service before investigating the root cause. section 11.0
• Inspect version-control history to identify the previously working change. section 11.1.1
• Use git revert to create and push a new configuration state through the IaC pipeline. section 11.1.1

Restoring a service permission

After removing roles/cloudsql.admin from the promotions service account, revert the commit and push the change. The pipeline adds the role back, producing a new working state without manual break-glass changes. section 11.1.1

Figure 11.2 You add the administrative database role for the promotions service to roll forward the system to a working state.

Shows the administrative database role being added back to restore the promotions service. section 11.1.1

How Infrastructure as Code, Patterns and Practices: With examples in Python and Terraform covers it

How deep it goes

Explains commit inspection, git revert, and pipeline application, but stops short of general troubleshooting internals.

Examples

Uses a removed database role, Git history, git revert, and static-analysis recovery as concrete examples.

What it assumes

Assumes infrastructure as code, version control, and deployment pipelines while emphasizing stabilization before root-cause debugging.

What you can do after

Operate IaC recovery by reverting commits and rolling forward a known-working configuration through the deployment pipeline.

How it connects

Connects rollback with infrastructure as code, immutability, GitOps, version control, and static analysis.

liveBookmanning.com

Read Infrastructure as Code, Patterns and Practices: With examples in Python and Terraform on liveBook Get the book at manning.com

Also explained in

• 

  liveBookmanning.com
  Machine Learning Platform EngineeringA rollback is the restoration of a deployed application to a previously functioning version.
• 

  liveBookmanning.com
  .NET in Action, Second EditionA rollback discards the changes made within a database transaction.
• 

  liveBookmanning.com
  Architecting an Apache Iceberg LakehouseAn operation that makes an earlier table snapshot the current state without necessarily deleting files introduced by later snapshots.
• 

  liveBookmanning.com
  Think Like a Software Engineering ManagerA rollback is the restoration of a software system or deployment to a previous known state after a change causes problems.
• 

  liveBookmanning.com
  Kubernetes in Action, Second EditionA rollback is the reversion of a deployed application workload to an earlier version or revision.
• 

  liveBookmanning.com
  Acing the Certified Kubernetes Administrator Exam, Second EditionRollback is the restoration of an application to a previous known configuration or version after a change.
• 

  liveBookmanning.com
  GitHub Actions in Action: Continuous integration and delivery for DevOpsRollback is the process of returning a deployment or system to a previously known good version or state.

Compare how 8 books explain rollback →

Related concepts

• roll-forwardcontrasts with · Roll-forward is a recovery technique that corrects a faulty or failed change by applying a subsequent corrective change rather than reverting to a previous state.
• database transactionpart of · A database transaction is a logical unit of database operations whose changes are committed together or rolled back as a whole.
• feature flaguses · A feature flag is a configuration control that conditionally enables, disables, or selects a software feature or behavior.
• versionuses · A version is a distinct, identifiable state or revision of an artifact, system, or product, often distinguished by its contents, behavior, or release identifier.
• deploymentaddresses · Deployment is the process of making software, models, or other computational systems available to operate in a target environment.
• TransactionalTestExecutionListenerused by · TransactionalTestExecutionListener is a Spring TestContext listener that manages transaction-related actions around test execution, including executing tests within transactions and rolling them back.

This explainer was generated by Manning's knowledge graph from the text of Infrastructure as Code, Patterns and Practices: With examples in Python and Terraform. The section links point to the parts of the book it draws on.