Q: Your Terraform plan wants to destroy and recreate a production RDS instance because you changed the instance identifier. How do you prevent the destroy?
Changing identifier for RDS forces replacement — Terraform deletes the old and creates a new one. That means downtime and potential data loss.
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."
Initial Diagnostics & Root Cause Analysis
Changing identifier for RDS forces replacement — Terraform deletes the old and creates a new one. That means downtime and potential data loss.
- Lifecycle ignore_changes:
- lifecycle prevent_destroy:
terraform state mv— rename the resource in state without destroying:
Remediation & Permanent Safeguards
Prevent destruction: This tells Terraform to ignore changes to the identifier field. Terraform will throw an error if anything tries to destroy this resource. Hard safety net. Update the config, then plan — Terraform sees the state and config match, no destroy needed.
lifecycle {
ignore_changes = [identifier]
}
- Lifecycle ignore_changes:
- lifecycle prevent_destroy:
- terraform state mv — rename the resource in state without destroying:
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 Terraform plan wants 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 Terraform plan wants 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 Terraform plan wants 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 Terraform plan wants Unpinned provider versions automatically download breaking major upgrades during CI runs, introducing unexpected schema validation failures.