With the latest release, Steampunk Spotter checks Terraform plans before apply, in addition to Terraform configurations at merge request. It enforces built-in checks and your custom policies on the resolved plan, flags secrets left in cleartext, and validates code against the definitions of official Terraform providers.
This closes the gap that code review leaves open. A reviewer sees what someone wrote, but the real change and any sensitive values in it only become visible once Terraform resolves the plan. Now Spotter checks both, inside the CI/CD pipeline you already run.
What’s new in Spotter for Terraform
Plan checks before apply
Spotter now scans the plan file that terraform plan -out produces. Built-in checks and your own custom policies run on the resolved values, after variables, modules, data sources and provider defaults are filled in. If a change breaks a policy, Spotter blocks it before terraform apply .
Here’s why that matters.…