Q: Your remote module source points to a Git branch, and a new commit on that branch changed production plans unexpectedly. How do you prevent this?
Pin module sources to immutable versions such as tags or commit SHAs. Use a release process for shared modules, test the new version in non-production first, and update module references intentionally.
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
Pin module sources to immutable versions such as tags or commit SHAs. Use a release process for shared modules, test the new version in non-production first, and update module references intentionally. Branch-based module sources are convenient during development, but they make production infrastructure depend on whatever code happens to be at the branch head.
- Immediate Triage: Pin module sources to immutable versions such as tags or commit SHAs. Use a release process for
- 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 remote module source 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 remote module source 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 remote module source 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 remote module source Unpinned provider versions automatically download breaking major upgrades during CI runs, introducing unexpected schema validation failures.