Skip to main content

Expose Full Dependency Tree and Root Run ID in Policies

Feature Requests

We are heavily using stack dependencies, and when one stack triggers many others, we need visibility into the full dependency chain inside policies.

Right now, we only have access to limited upstream information. It would be very helpful if every policy type, including notification policies, had access to the full dependency tree and the root run ID.

This would allow us to:

  • Track who originally started the run

  • Thread Slack notifications properly

  • Reference the same root run across all dependent stacks

  • Build cleaner approval and notification logic

Currently, we have to rely on workarounds and custom scripting. Having full dependency visibility in policies would simplify our setup significantly.

Status: ⬆️ Gathering votes2 comments

Log in to comment and vote

Comments2

  • Coral Chipmunk

    •

    Mar 18

    Hi @Marcin Wyszynski , the root run ID would be the priority but there could be some additional benefits in seeing the full tree. For example strict enforcement of dependencies that mush run at the policy level vs just through the dependency feature.

    A similar discussion is here as well:

    https://feedback.spacelift.io/u/67b27db6cef54eac61d9dc8f

  • Black Breeze

    •

    Mar 17

    @Rob Put thanks for raising this. Reading and re-reading your feature request I can’t help but wonder - do you actually need the entire tree, or would the “root run” be enough? Is there a situation where you’d actually need to walk the entire dependency tree in any particular policy? My intuition that for the first three use cases you only need to group by root, not sure about the last one?