Q: Your plan fails because a data source cannot find a resource that is created in the same apply. Why does this happen?
Data sources read existing infrastructure during planning, before new resources are created. If the object does not already exist, the lookup fails.
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: "Treat Terraform code with the same rigor as application code: pre-merge plans, state locks, and automated drift detection. 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
Data sources read existing infrastructure during planning, before new resources are created. If the object does not already exist, the lookup fails. Use direct references to the managed resource instead of a data source when both live in the same configuration, or split the workflow into stages if the dependency truly must be read after creation.
- Immediate Triage: Data sources read existing infrastructure during planning, before new resources are created. If
- 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 plan fails data 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 plan fails data 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 plan fails data 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 plan fails data Unpinned provider versions automatically download breaking major upgrades during CI runs, introducing unexpected schema validation failures.