Use case
Drift Reconciliation
Continuously detect infrastructure drift across Terraform/OpenTofu and connected clouds, then reconcile safely via governed workflows.
Infrastructure drift is the gap between what your IaC declares and what your cloud actually contains.
In practice, drift appears when someone changes something in the cloud console, when automation adjusts configuration, or when infrastructure evolves without keeping IaC perfectly updated.
The control loop
OrchesTerra runs a continuous workflow:
- Scan your declared IaC state (Terraform/OpenTofu).
- Compare to live cloud inventory.
- Classify findings by severity and remediation type.
- Produce remediation options: import, reconcile, or accept temporarily.
- Route remediation through approval workflows when risk is meaningful.
- Reconcile using an auditable plan context.
Why classification matters
Not all drift needs the same response:
- Security-critical drift requires fast, reviewed reconciliation.
- Reliability-critical drift needs investigation before impact.
- Hygiene drift is often better handled via planned improvements.
OrchesTerra capabilities involved
FAQ
What kinds of drift can you detect?
Changes to configuration, unmanaged resources, and mismatches between expected and actual state—across multiple cloud providers.
How do you prevent “fixing drift” from creating new drift?
By reconciling using a plan that reviewers can understand, and by routing risky changes through approvals and governance signals.