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

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.

WorkaroundNo
ProblemAllowing approval policies or plan policies to be more specific by including the entire dependency tree.

Please authenticate to join the conversation.

Upvoters
Status

⬆️ Gathering votes

Category

💡 Feature Requests

Labels

Access Control

Date

14 days ago

Subscribe to request

Get notified by email when there are changes.