Hey, 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.
Black Breeze
•
May 7, 2025
Hey! Quick question to better understand your request—when you say you want to “force trigger drift detection” on a stack or multiple stacks, what are you trying to achieve in that moment?
Would running a tracked plan (with diff, audit trail, and policy checks) give you what you need?
Log in to comment and vote
Comments2
Natalia Gazda
Jul 16
Hey, 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.
Black Breeze
May 7, 2025
Hey! Quick question to better understand your request—when you say you want to “force trigger drift detection” on a stack or multiple stacks, what are you trying to achieve in that moment?
Would running a tracked plan (with diff, audit trail, and policy checks) give you what you need?
If not, what would success look like for you?