Skip to main content

Add ability to group stacks

The same module can be used to create various stacks. That is one for production, one for staging environment for example. It would be great to be able to group such stacks together or at least linked them in a way.

It will allow for instance while on stack details page to quickly switch to the “same” stack but for another configuration thanks to a dropdown.

Workaround
No
Status: 🗑️ Archived7 comments

Log in to comment and vote

Comments7

  • Natalia Gazda

    Team•

    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 10, 2025

    Thanks for the idea! We’d love to understand the job you’re trying to get done.

    It sounds like you’re creating multiple stacks from the same module and want a better way to switch between them. Could you tell us more about the why behind that? For example:

    • Are you trying to compare environments like dev/staging/prod?

    • Do you need to coordinate changes across similar stacks?

    • Is this about faster navigation, or shared lifecycle?

    Understanding the outcome you’re after will help us find the simplest and most useful way to support it—whether that’s “grouping,” quick linking, or something else.

    Thanks again for helping shape Spacelift!

    • Azure Breeze

      •

      May 12, 2025

      Hi, thx for asking.


      Well, I would like to answer yes to your 3 bullets points.


      When I’m editing a module, I create a Pull Request on Github. Within the PR, I can see one check per stack associated to the module. I’m used to check each modification for each stack. So for now my workflow is:

      • Within my PR, click on the checks tab

      • Select a check associated to a stack

      • Click on the link to open the Spacelift run page

      • Review

      • Go back on the Github checks tab

      • Select another check

      • Click on the link to open the Spacelift run page

      • etc

      For stacks that are not related, this is workflow is ok. But be able to quickly jump from stack to another when “sibling” will save me so many time.

      Another solution would to be able to list all the stacks impacted by a Pull Requests directly from Spacelift.

  • Natalia Gazda

    Team•

    Apr 23, 2025

    Hey, @Thibaut ETIENNE, thanks for submitting that! Are you aware of our labelling functionality? Here and here is the documentation link. Please let me know whether that works for you!

    • Azure Breeze

      •

      Apr 28, 2025

      Thank you for sharing the links, @Natalia Gazda. I was unaware of this folder magic label. It does seem useful for my request, but it doesn't fully address my last wish
      > It will allow for instance while on stack details page to quickly switch to the “same” stack but for another configuration thanks to a dropdown.

      • Natalia Gazda

        Team•

        Apr 28, 2025

        @Thibaut ETIENNE alright got it. What if the labels in stack details were clickable? And took you to a stack list with the filter for the label. Would that work?

        • Azure Breeze

          •

          Apr 29, 2025

          That would be at least an improvement yes.