A single misconfiguration can push your infrastructure out of sync with your code, and you won’t see it until something breaks. That gap is called drift. Detecting it fast is the difference between control and chaos.
IaC drift detection TTY is the practice of running infrastructure-as-code drift checks directly in a terminal interface. Instead of waiting for a pipeline or external scanner, the detection happens in real time where you work. This makes drift visible the moment it occurs, before it has a chance to propagate.
Infrastructure drift happens when deployed resources no longer match the definitions in your IaC templates. Manual changes, emergency patches, or untracked automation can introduce differences. They build up silently. The risk is high: security holes, unexpected costs, and broken deployments.
A TTY-based drift detection flow connects to your IaC backend and queries the actual state. It compares that state against the source-of-truth code. Results show in your CLI instantly, often with direct pointers to what changed — new resources, altered parameters, or missing items. This speed matters. You can respond immediately, commit fixes, or roll back changes before they spread.