Q: During an incident, someone suggests using `terraform apply -target` to update only one resource. When is that acceptable?
target can be useful for a narrow recovery action, such as recreating one broken dependency, but it should not become a normal deployment method.
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
-target can be useful for a narrow recovery action, such as recreating one broken dependency, but it should not become a normal deployment method. It bypasses Terraform's full graph planning, so related resources may be left inconsistent. After the emergency action, run a normal terraform plan for the whole root module and reconcile any remaining changes.
- Immediate Triage: -target can be useful for a narrow recovery action, such as recreating one broken dependency, b
- 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 incident someone suggests 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 incident someone suggests 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 incident someone suggests 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 incident someone suggests Unpinned provider versions automatically download breaking major upgrades during CI runs, introducing unexpected schema validation failures.