Propagate blueprint changes to affected stacks
Right now if you update a blueprint, the stacks that have been created from it don’t get updated. This is a very safe feature, but in some automation cases it’d be more helpful to be able to change the blueprint and get the change propagated to all stacks that have been created from it.
- Workaround
- No
- Problem
Log in to comment and vote
Comments1
Aleksandra Cieslak
Jul 9
Hi,
Thanks for the feature request. This is a great use case to test against something we recently shipped: Templates.
Unlike Blueprints, Templates keep an ongoing, versioned link to every stack they create. You publish a new Template version, then update deployments to that version, so changes can propagate in a controlled way, instead of blueprint edits being a one-time snapshot.
Two things to flag before you try it:
It's on the Business plan and above.
Updating is currently per-deployment (scriptable via API/Terraform), not a single "push to all stacks" action yet.
I'd encourage you to give the templates a try and let us know what you think!
More info here:
https://docs.spacelift.io/concepts/template