liveBook · Manning

Change management

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

A governance process of steps and reviews for implementing production changes while controlling their risk.

Change management governs production changes through documented steps and reviews that control risk, conflicts, and effects on security or availability. section 1.4.1 section 7.0

A practical change-management flow:

  • Submit a change request describing the implementation, rollout, and rollback steps. section 7.0
  • Use peer review and a change advisory board as quality gates for security, availability, resiliency, and conflicting work. section 7.0
  • Schedule the approved change, execute it during an appropriate window, and verify its result. section 1.4.1
  • Reduce residual risk with reproducible tests, idempotent checks, composable scope, and infrastructure that can evolve consistently. section 1.4.1
Figure 7.1 Collaboration on IaC involves streamlining the process of peer and organizational review of changes.

Use the collaboration workflow to see how peer and organizational review coordinates conflicting infrastructure changes. section 7.0

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

How deep it goes
Defines the workflow and risk controls, but stops short of automating every review or preventing every failure.
Examples
Uses server changes, ticketed requests, conflicting updates, change windows, and an incompatible binary rollout.
What it assumes
Assumes production infrastructure, peer collaboration, review authority, and familiarity with infrastructure-as-code practices.
What you can do after
Operate/configure production changes with documented rollout and rollback plans, coordinated approvals, and explicit risk mitigation.
How it connects
Connects infrastructure as code, peer review, quality gates, continuous delivery, and GitOps.

Also explained in

Compare how 4 books explain change management →

Related concepts

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.