Choose the state and ownership boundary that preserves the intended remote object. Check a plan against actual inventory, backend access, and the receiving team's run before approving a handoff.
Review these lessons
- Terraform provider locks: review the executable dependency
- Terraform import: adopt one existing object under one state owner
- Terraform replacement: prove old and new can coexist
- Terraform state locks: distinguish a stale lease from an active writer
- Terraform state secrets: redaction is not removal
- Terraform collection keys: keep resource identity stable through reorderings
- Terraform ignore_changes: name the second owner of every ignored field
- Terraform state removal: hand off an object without deleting it
Other checks
Common Mistakes
- Do not infer module pinning from a provider lock.
- Do not treat a state removal as automatic transfer of operations.