Q: Your team renamed a variable in a shared module and now all consuming environments fail during `terraform plan`. How do you roll out that change safely?
Treat module input changes as an interface change. First add the new variable while still supporting the old one, and map both to the sam...
#Terraform #Use VPC ID from another module #L2 #IaC #Cloud Infrastructure
🎙️ Candidate Opening & Architectural Context
""Managing infrastructure as code across multiple teams requires disciplined state management and locking. 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
Treat module input changes as an interface change. First add the new variable while still supporting the old one, and map both to the same internal value temporarily. Update consumers environment by environment, run plan in each one, and only remove the old variable after every caller has migrated. For widely used modules, version the module and release the breaking change in a new major version.
💡 The Senior SRE Gold Nugget (Key Architectural Takeaway)
"Pro-Tip: Treat module input changes as an interface change. First add the new variable while still supporting the old one, and map both to ."
⚡ 60-Second Elevator Pitch Talking Points
- Immediate Triage: Treat module input changes as an interface change. First add the new variable while still suppo
- Run targeted verification commands before modifying configuration.
- Automate permanent guardrails (CI check, alerts, IaC policy) to prevent recurrence.
Advertisement