The Iac Drift Detection feature request is gaining traction because teams need a reliable way to know exactly when their infrastructure-as-code has drifted from the version in source control. This gap between declared state and actual state can cause outages, security holes, and unplanned costs.
Iac drift detection scans live resources, compares them to the IaC definition, and reports changes that were introduced outside the IaC workflow. It flags unauthorized edits, manual hotfixes, and forgotten resource tweaks before they spiral into bigger issues. It works across cloud environments where Terraform, Pulumi, or AWS CloudFormation define the intended state, but real-world operations sometimes break that contract.
The strongest feature requests center around real-time detection and clear, actionable reports. Engineers want configurable scan intervals, API endpoints for custom integrations, and severity tagging. They also want automatic remediation modes, where drift can be reverted or staged for approval before rollout. Trust in automation hinges on accuracy and zero false positives; a clean signal is more important than noisy alerts.