Terramate CLI ↔ GitHub Actions: Defining Drift Severity and Deduplication for Low‑Noise Alerts

Goal

Turn Terramate’s experimental drift detection output into actionable notifications that highlight meaningful infrastructure drift while keeping alert volume low in a multi‑stack Terraform environment.

Constraints

Terramate’s drift detect command is experimental and returns a flat list of drifted resources without a severity taxonomy, and it provides no built‑in deduplication or stateful suppression across pipeline runs. When using Terramate Cloud, the webhook payload for drift events is not versioned in public documentation, so the exact fields and their types may change between releases.

Open Questions

1. What criteria can be applied to the raw drift output to distinguish critical from informational drift?
2. How can a CI/CD layer reliably suppress repeat alerts for the same drifted resource without external state storage?
3. Which approach ensures stable consumption of Terramate Cloud drift webhooks given the undocumented payload schema?