Q: What is terraform taint, when would you use it, and why did Terraform 0.15.2+ introduce terraform apply -replace to supersede it?
Understanding terraform taint vs terraform apply -replace: marking degraded infrastructure for recreation, avoiding state file mutation, and safe workflows in collaborative teams.
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."
Initial Diagnostics & Root Cause Analysis
terraform taint marks a resource for destruction and recreation on the next terraform apply. Even if nothing in the config changed.
- A resource is in a broken/inconsistent state in the cloud but Terraform's state says it's fine.
- You want to force recreation of an EC2 instance to apply a new AMI (for resources that can't be updated in-place).
Remediation & Permanent Safeguards
Use cases: In Terraform 0.15.2+, terraform taint is replaced by terraform apply -replace= which is more explicit. Note: tainting deletes and recreates. For stateful resources (databases, volumes), this means data loss. Be careful.
- A resource is in a broken/inconsistent state in the cloud but Terraform's state says it's fine.
- You want to force recreation of an EC2 instance to apply a new AMI (for resources that can't be u...
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 Taint replace 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 Taint replace 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 Taint replace 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 Taint replace Unpinned provider versions automatically download breaking major upgrades during CI runs, introducing unexpected schema validation failures.