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 same internal value temporarily.
Want to master this scenario in a live sandbox? KodeKloud's HashiCorp Certified Terraform Associate (003) Interactive Labs covers this exact problem with hands-on terminal drills.
🛠️ Production Runbook & Step-by-Step Resolution
Direct Answer: "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."
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.
- 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.
Senior hiring managers and bar raisers evaluate how you prioritize during outages. Avoid these common anti-patterns:
- Executing Terraform applies without inspecting '# forces replacement' warnings in plan output when configuring team renamed variable Attributes that force resource replacement destroy and recreate critical infrastructure (databases, load balancers), inducing unannounced production outages.
- Omitting remote state locking mechanisms (DynamoDB or backend native locks) for shared state files when configuring team renamed variable Without state locking, concurrent CI/CD pipeline executions or team applies create race conditions that corrupt the state file.
- Structuring entire enterprise cloud footprints into a single monolithic Terraform root module when configuring team renamed variable Monolithic state files slow plan execution dramatically, increase blast radius during failed applies, and create severe pipeline locking contention.
- Failing to pin required_providers versions, causing breaking provider upgrades in CI pipelines when configuring team renamed variable Unpinned provider versions automatically download breaking major upgrades during CI runs, introducing unexpected schema validation failures.