Most teams discover Terraform drift the hard way — someone runs terraform plan before a deploy and gets a screen full of unexpected changes. By then the drift might have been sitting there for weeks. Maybe longer.
What if you could catch it automatically? Run a scan every few hours, get a Slack message only when something important drifts, and ignore the noise?
That's what this tutorial sets up. By the end, you'll have:
A GitHub Actions workflow that scans your Terraform infrastructure on a schedule
Slack alerts that only fire for High and Critical severity drift
