Q: A Terraform apply introduced a bad infrastructure change in production. What is the rollback process?
Revert the Terraform code to the last known good version and run a new plan to see what Terraform will change back. Apply that reviewed r...
#Terraform #Use VPC ID from another module #L3 #IaC #Cloud Infrastructure #Terraform State
🎙️ Candidate Opening & Architectural Context
""Treat Terraform code with the same rigor as application code: pre-merge plans, state locks, and automated drift detection. When addressing this question, I walk the interviewer through our production incident runbook: isolating the blast radius, checking diagnostic logs and metrics, and applying a safe fix.""
Advertisement
🛠️ Production Runbook & Step-by-Step Resolution
1️⃣
Production Solution & Architecture
Revert the Terraform code to the last known good version and run a new plan to see what Terraform will change back. Apply that reviewed rollback plan through the normal approval path unless the incident process allows emergency approval. Restore state only if the state itself is wrong or corrupted; for a bad but successful infrastructure change, state usually reflects reality and the fix is another controlled apply. --- *More Terraform scenarios added periodically. PRs welcome.*
💡 The Senior SRE Gold Nugget (Key Architectural Takeaway)
"Pro-Tip: Revert the Terraform code to the last known good version and run a new plan to see what Terraform will change back. Apply that rev."
⚡ 60-Second Elevator Pitch Talking Points
- Immediate Triage: Revert the Terraform code to the last known good version and run a new plan to see what Terrafo
- Run targeted verification commands before modifying configuration.
- Automate permanent guardrails (CI check, alerts, IaC policy) to prevent recurrence.
Advertisement