Q: You need to import dozens of existing resources into module paths using Terraform import blocks. How do you make the import manageable?
Write the target module configuration first, add one import block per resource address, and import in small batches. After each batch, run terraform plan and adjust the HCL until Terraform shows no unexpected changes.
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
Write the target module configuration first, add one import block per resource address, and import in small batches. After each batch, run terraform plan and adjust the HCL until Terraform shows no unexpected changes. For resources with immutable attributes, match the existing cloud configuration before the first apply. Large imports are state migrations, so review them like production changes.
- Immediate Triage: Write the target module configuration first, add one import block per resource address, and imp
- 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 need import dozens 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 need import dozens 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 need import dozens 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 need import dozens Unpinned provider versions automatically download breaking major upgrades during CI runs, introducing unexpected schema validation failures.