Skip to main content

Manage Multiple Stacks as a Collection With Centralized Configuration

Feature RequestsStacks

Problem Statement & Use Case

Currently, Spacelift users must manage Stacks independently, which is complex and inefficient for organizations deploying, updating, or retiring groups of related infrastructure resources. There is no native way to treat multiple Stacks as a unified collection, centrally manage their configuration, or handle lifecycle operations (creation, update, deletion, dependencies) as a group.


Proposed Solution

Introduce a “Collection” or “Stack Group” feature to:

  • Group multiple Stacks and maintain their configuration in a single place.

  • Allow centrally manage the configuration for the group (ideally with nice UI) and propagate configuration updates to all member Stacks. A non-technical person should be able to modify the configuration.

  • Create special UI views to track deployment of Stacks inside the collection.

  • Support adding and removing Stacks from the collection, with lifecycle events (creation, update, deletion) tracked and applied consistently.

  • Enable defining dependencies between Stacks in a collection, with safe orchestration of deployment order.

Workaround
No workaround
2 comments

Log in to comment and vote

Comments2

  • Aleksandra Cieslak

    Team•

    Jul 20

    Hi, thanks for the detailed write-up!

    Going through it, a lot of what you're describing maps closely to our existing Templates functionality:

    • Grouping multiple Stacks and managing their configuration in one place — this is essentially what a Template + deployment gives you today.

    • Centrally updating configuration and propagating it to member Stacks — updating a deployment (or publishing a new template version) rolls the change out to the Stacks created from it.

    • A dedicated view to track deployments across a group of Stacks — we have a Stacks list view scoped to a given deployment for this.

    • Defining dependencies between Stacks with safe orchestration — this can be configured directly within a template.

    So before we scope any new work, we'd like to understand where the gaps actually are for you.


    Would you be up for a ~30 min call so we can walk through your setup together and see how much of this Templates already covers vs. where a real gap exists?

    Here's my calendar, feel free to grab a slot that works for you: https://calendar.app.google/xowV6MPR7qt6FjEu9

    If none of the times work, just let me know and I'll find another slot.

  • Yellow Coral

    •

    Jan 15

    For us, it’d be tremendously helpful to be able to set stack level settings on a Space level, and all of those stack inherits from that Space config.

    We group stacks with Spaces already, and most of them have similar configs, for example, the “Prod” Space will always have Autodeploy to off.

    Right now, we are configuring that with Terraform. But if set at the Space level, I think that is cleaner.