Search⌘ K
AI Features

Drift Detection With Refresh-Only Planning

Understand how to investigate infrastructure drift without changing production. Learn how refresh-only planning compares recorded state with provider data, what evidence to capture, how to frame blast radius and urgency, and why intent or cause must remain unverified until independently checked.

A plan that suddenly proposes changes nobody made in code can signal drift between the recorded state and the actual resource. In an interview, the safest first step is to detect and describe the mismatch without making any changes to production.

Drift occurs when a managed resource changes outside the infrastructure-as-code workflow, leaving the recorded state stale. A refresh reads the provider’s current view of the resource; a refresh-only plan then shows how the record would change to match that reality. It does not establish who made the change, when ...