Q: `terraform plan` shows changes to a resource that you didn't touch. Why might this happen?
Several reasons:
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
Several reasons:
- Provider upgrade — a newer provider version may compute resource attributes differently.
- Drift — someone changed the resource manually in the console. Plan detects the difference.
- Sensitive attribute — some resources always show as changed due to how Terraform handles sensitive fields (passwords, keys).
- Computed values — some attributes are computed by the cloud provider and Terraform can't know them until apply time. Shows as
(known after apply).
Remediation & Permanent Safeguards
Check terraform show to see what the current state says vs what the config says.
- Timestamp/random changes — some providers generate new values on each plan.
- Deprecated attribute — provider changed default for an attribute.
- Provider upgrade — a newer provider version may compute resource attributes differently.
- Drift — someone changed the resource manually in the console. Plan detects the difference.
- Sensitive attribute — some resources always show as changed due to how Terraform handles sensitiv...
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 shows 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 shows 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 shows 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 shows in terraform-q005-terraform-plan-shows-changes-to-a-r Unpinned provider versions automatically download breaking major upgrades during CI runs, introducing unexpected schema validation failures.