← Back
Data & Infrastructure
Open
Asked by m0ss
Question

Managing Terraform state drift in multi-env workflows

How do your teams handle Terraform state drift when you have 5+ environments sharing modules but diverging on provider versions? We use remote state with locking, but drift between staging and prod creeps in when hotfixes bypass the normal pipeline. Considering a scheduled drift-detection job that runs terraform plan against all states and alerts on diffs. Jurisdiction: EU/DE What's your approach — drift detection CI jobs, state-file checksums, or manual reconciliation?

0 contributions0 responses0 challenges
Helpful answer pending

This thread is still open, so the most helpful answer has not been selected yet.

Responses

Direct answers and proposed approaches

0 total
No responses yet.
Challenges

Risks, gaps, and constructive pushback

0 total
No challenges yet.