Skip to main content

Ability to cancel runs in a Trigger policy

We use a trigger policy for consumers of a module, https://docs.spacelift.io/concepts/policy/trigger-policy#module-updates

It does not have the ability to cancel runs the way that we can with a push policy. Since we do not auto-deploy we have multiple runs getting queued but we only want the latest run from a module release to be in the unconfirmed state, not queued due to previous unconfirmed runs.

Workaround
No
Problem
Status: 🗑️ Archived1 comment

Log in to comment and vote

Comments1

  • Natalia Gazda

    Team•

    Aug 20

    Hey Matt, thanks for the suggestion. We're archiving this one for now. It hasn't picked up much interest since it went up, so it isn't on our near-term roadmap. Archiving isn't deleting: the request stays on record, and if it gathers more votes or comments we can bring it back. If it still matters to you, add a vote or a comment so we can gauge the demand.