Preventing permanent drift
In Terraform, it is sometimes possible for a freshly applied component to have drift. This can happen for several reasons, including non-idempotent data sources or provider bugs.
Atmos Pro now includes a repository-level Verify drift after apply setting that dispatches drift detection after successful apply and remediation runs.
When the setting is enabled, Atmos Pro immediately dispatches the configured drift detection workflow for the same stack and component after an apply succeeds. The component moves into a checking state while that verification runs, then the Drift view updates from the follow-up plan result.
Enabled by default, safe when detection is not configured
The setting is enabled by default for each repository and lives in the repository settings Drift tab above Drift Detection Schedules. Repository owners and admins can disable it if they prefer apply success to update drift status directly.
Post-apply verification only runs when a component has a configured detection workflow. If no detection workflow exists, Atmos Pro skips the verification run and keeps the apply-derived status instead of leaving the component stuck in checking.
Applies to remediation too
The same behavior applies to drift remediation. After a remediation apply succeeds, Atmos Pro can immediately dispatch detection again so the final drift status reflects what a fresh plan sees, not only that the apply command exited successfully.
