Skip to main content

Drift detection run only when last tracked run was x hours ago

Feature RequestsDrift Detection

Instead of, or perhaps in addition to the cron schedule:

Some stacks are quite frequently updated, while others are more “stable” (this can shift in time). Having drift detection is good, but a bit overkill when the stack just got updated.

In combination with large amounts of stacks, this would for more effective / frequent drift detction for the relevant stacks.

Status: ❌ Rejected1 comment

Log in to comment and vote

Comments1

  • Black Breeze

    •

    May 10, 2025

    Thanks for the thoughtful suggestion! We’ve considered a “cooldown window” after tracked runs to suppress drift detection, but we’re holding off for now.

    Why?

    • Drift can happen at any time—even right after a tracked apply. Suppressing checks based on timing adds risk.

    • The complexity cost is high for something that doesn’t solve a painful or urgent problem.

    • Drift detection is already optional and efficient enough for most teams today.

    We’ll keep listening, but for now we’re optimizing for safety and simplicity.