Q: Your team used human-readable names as `for_each` keys, and renaming `prod-web` to `production-web` now wants to recreate resources. How do you avoid this?
Use stable, non-display keys for for_each, such as logical IDs that do not change when labels change. Keep the human-readable name as an attribute inside the object.
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: "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."
Production Solution & Architecture
Use stable, non-display keys for for_each, such as logical IDs that do not change when labels change. Keep the human-readable name as an attribute inside the object. For an existing rename, use moved blocks or terraform state mv to map the old address to the new address before applying. The key is part of the Terraform resource address, so changing it is a state migration.
- Immediate Triage: Use stable, non-display keys for for_each, such as logical IDs that do not change when labels c
- 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 used human 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 used human 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 used human 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 used human Unpinned provider versions automatically download breaking major upgrades during CI runs, introducing unexpected schema validation failures.