Codify or Revert: The Drift Decision Fork
After detecting drift between declared configurations and actual infrastructure, teams face a critical decision: to codify the change as the new standard or revert to the original configuration. Codifying accepts the live change as valid, requiring approval and ensuring future compliance, while reverting treats the change as unauthorized and restores the previous state. Each path involves considerations of authorization, risk, and verification to maintain service stability and compliance with standards. The decision hinges on the nature of the change, its necessity, and the potential impact on operations.
We'll cover the following...
After drift is detected, the key question is whether the out-of-band change should become the new declared configuration or whether the real infrastructure should return to the existing declaration. A strong decision weighs authorization, auditability, stabilization time, verification, and reversibility against the service requirement the resource supports.
Drift is a difference between declared configuration and the real resource. In a Terraform-family workflow, a refresh-only plan can reconcile recorded state with the remote object without changing that object; the team still must decide whether to update configuration or reapply configuration to restore the declared value.
The ...