Drift detection for building blocks
in progress
J
Johannes Rudolph
As a platform team we'd like to monitor the health of deployed building blocks, especially whether there is any unwanted drift. Drift can occur due to side administration, immature terraform practices (e.g. missing lifecycle ignore_changes), or an unclear shared responsibility
This ticket is to collect community feedback on common challenges you have with drift detection like
- choosing an automatic or manual reconciliation strategy for drift
- what kind of reporting on drift you'd like to see
Andreas Grub
Update — June 2026
A quick note on where we are: the foundational work for drift detection is progressing alongside the dry-run feature, which is closely related. The current cycle (demo on June 17th) delivers the manual dry-run capability and a major overhaul of the building block list and runs view. Indicating detected changes as drift in the UI is not yet included in this cycle.
Automatic drift detection and the ability to define reconciliation policies are planned for the next cycle. We will update this post once we have more to share.
Andreas Grub
Update — June 2026
A quick note on where we are: the foundational work for drift detection is progressing alongside the dry-run feature, which is closely related. The current cycle (demo on June 17th) delivers the manual dry-run capability and a major overhaul of the building block list and runs view. Indicating detected changes as drift in the UI is not yet included in this cycle.
Automatic drift detection and the ability to define reconciliation policies are planned for the next cycle. We will update this post once we have more to share.
Jelle den Burger
marked this post as
in progress
We are working on this right now.