Skip to main content

The ability to see `triggered_by` for the entire dependency chain.

Feature RequestsAccess ControlStacksPoliciesStack Dependencies

Currently when making any policy and a stack is triggered by another stack you only see one triggered_by .

If you have more than one layer of apps that depend on the very first stack needing an approval, and you want to auto-approve the dependent stack there isn’t a clean way to say if it was triggered by this job since the triggered_by won’t have any information on what the root stack is.

The ask is similar to https://feedback.spacelift.io/p/include-the-runid-of-an-upstream-stack-and-any-other but just always for triggerred_by .

Where currently run_id is recursive and you can use the OPA walk function to get the data.

Workaround
No
Problem
Status: 🔭 Discovery1 comment

Log in to comment and vote

Comments1

  • Natalia Gazda

    Team•

    Sep 11

    Hey @Peter Rakhunov thank you for the request! We have in mind to make an upgrade of our stack dependency feature at some point, so I tagged it properly, but it’s not something we’re doing at this very moment. I’m changing it to “Gathering votes”, to see if there’e more demand, and we might get back to it, once we pick up the stack dependencies topic :)