Support promoting Blueprint changes from staging to production
Jennifer Hwang
I have 2 branches - 1 for staging and 1 for production (master). After changes have been tested in staging, I merge the staging branch into master. This works pretty well except in cases where I need to make changes in Blueprint such as changing the value of an environment variable.
Currently, to do the change safely, I have to:
- Update the staging value, deploy it to staging for testing.
- Make a second code change to update the production value.
- Merge staging branch into master
I'd like to deploy to staging selectively and have only staging code and environment settings updated. When I merge to master, that's when I'd like the changes to be propagated to production
A more comprehensive example and explanation can be found here: https://community.render.com/t/best-practices-using-blueprints-in-a-production-staging-environment-setting/4415/4
Log In
J
Jurgis Petrauskas-Mittas
Same here. We want to use blueprints yamls for each env but this is blocking us.
p
pete
I'm in the same situation and it's keeping us from being able to use blueprints. It'd be great to see something like this get added!