Q: A pipeline was killed during `terraform apply`, and now every run fails because the state lock is still held. What do you do?
Confirm that no Terraform process is still running and that the previous apply is not active in the backend. Then use terraform force-unl...
#Terraform #Use VPC ID from another module #L2 #IaC #Cloud Infrastructure #Terraform State
🎙️ Candidate Opening & Architectural Context
""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.""
Advertisement
🛠️ Production Runbook & Step-by-Step Resolution
1️⃣
Production Solution & Architecture
Confirm that no Terraform process is still running and that the previous apply is not active in the backend. Then use terraform force-unlock with the lock ID from the error message. After unlocking, run terraform plan to verify the real state before applying again. Never force-unlock casually; it exists for abandoned locks, not for bypassing another active deployment.
💡 The Senior SRE Gold Nugget (Key Architectural Takeaway)
"Pro-Tip: Confirm that no Terraform process is still running and that the previous apply is not active in the backend. Then use terraform fo."
⚡ 60-Second Elevator Pitch Talking Points
- Immediate Triage: Confirm that no Terraform process is still running and that the previous apply is not active in
- Run targeted verification commands before modifying configuration.
- Automate permanent guardrails (CI check, alerts, IaC policy) to prevent recurrence.
Advertisement