Skip to main content

Cancel schdeduled drift detection run when there is tracked run for it being processed

Feature RequestsDrift Detection

Drift detection runs are added to the queue just on the cron schedule, in a low prio state.

When for such a scheduled stack, a tracked run is already in the queue, or added to it, the drift detection run is not removed.

Goven the drift detection run is scheduled with a commit sha, that is not up to date any more when new tracked runs are added, this wil cause some flipping issues in applying changes / perceived drifts.

Combined with drift detction only after x amount of time, this allows for more frequent drift detction schedules while at the same time removing a lot of unneeded runs. Esp in large volume stacks with high volume of changes…

Status: 🗑️ Archived1 comment

Log in to comment and vote

Comments1

  • Natalia Gazda

    Team•

    Sep 16

    Thanks for raising this, and to everyone who upvoted. It's been open for a while without gaining much upvotes, so I’m closing it for now while we focus on higher-priority work.

    It's not gone for good. If demand grows or priorities shift, we may revisit. If it still matters to you, leave a comment with your use case so we can gauge interest.

    Thanks for the feature request :)