Skip to main content

show dependencies that are triggered by a run

Feature RequestsUI/UX

in the same way you can see what run triggered a run in a dependent stack, seeing the inverse relationship on the “dependent-on” stack run would be good to alert users to what runs have been triggered by the current run more easily.

Workaround
Problem
Status: ✅ Completed3 comments

Log in to comment and vote

Comments3

  • Silver Pretzel

    •

    Apr 28

    is this just for dependency references? does it work in cases where a stack has a spacelift_run resource?

  • Black Breeze

    •

    May 10, 2025

    Thanks for sharing this—makes total sense on the surface, but we want to dig a bit deeper before we commit.

    We’re curious: what job are you trying to get done when you want to see which downstream stacks a run would trigger? Is it about:

    • Avoiding accidental changes to prod?

    • Coordinating with other teams?

    • Debugging something that ran unexpectedly?

    • Gaining confidence before kicking off a workflow?

    Each of these would pull the design in a slightly different direction (and might suggest different solutions too). If you can share a real scenario or two—especially where not having this visibility caused pain—that would really help us shape the right fix.

    Thanks again for helping us make Spacelift more predictable and transparent.

    • Azure Chipmunk

      •

      Jun 11, 2025

      Not the OP, but I don’t think they’re talking (necessarily) about dependency runs that will be triggered, but ones that have been triggered (once the first run is complete).

      For me personally, that particular feature would be useful so that I can easily open the downstream dependency runs to monitor their progress. We have a number of stacks that operate in “chains” of dependencies. Triggering a run in one of the “lower” layers of dependents will kick off runs in all the “upper” layers automatically and I would like to monitor their progress easily. Currently, the only way to do that is to back out of the “source” run and go to the “dependencies” tab and open up each of the dependents (recursively) and find the triggered run in the list. It’d be nice to have a shortcut to that triggered run directly.