Q: You changed a resource from `count` to `for_each` and Terraform now wants to recreate everything. How do you avoid that?
The resource addresses changed, so Terraform thinks the old objects disappeared and new ones must be created. Preserve state by moving addresses with terraform state mv, or use moved blocks if the mapping is straightforward.
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: "When terraform plan shows unexpected changes, my golden rule is: never apply blindly. Investigate the diff first. 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
The resource addresses changed, so Terraform thinks the old objects disappeared and new ones must be created. Preserve state by moving addresses with terraform state mv, or use moved blocks if the mapping is straightforward. Do the refactor in a controlled sequence: update code, move state entries one by one, then run terraform plan until it shows no infrastructure replacement.
- Immediate Triage: The resource addresses changed, so Terraform thinks the old objects disappeared and new ones mu
- 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 changed resource count 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 changed resource count 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 changed resource count 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 changed resource count Unpinned provider versions automatically download breaking major upgrades during CI runs, introducing unexpected schema validation failures.