Terraform: upgrade a provider without uncontrolled drift
A production runbook for qualifying a Terraform provider upgrade with a lockfile, baseline plan, canary, operational evidence and an explicit rollback.
Read article
Tag
6 articles connected to this technical signal.
A production runbook for qualifying a Terraform provider upgrade with a lockfile, baseline plan, canary, operational evidence and an explicit rollback.
Read articleA production runbook for qualifying a Terraform, Bicep or ARM plan before apply with drift, CI identity, Azure Policy, destructive changes, validation and rollback.
Read articleBuild an operational drift reading across Terraform, Private Endpoint, private DNS, CI runners, and validation evidence before a private Azure path breaks in production.
Read articleA short check to compare the expected DNS chain, returned private address, and test path from a workload or CI runner.
Read articleA short procedure to qualify a stuck Terraform lock, confirm that no apply is still active, and restart with a clean plan.
Read articleDesign an Azure Terraform backend based on a private Storage Account with CI identity, controlled network access, locking, separate bootstrap, and a diagnostic runbook when init or plan fails.
Read article