Hi all, currently our team encountered a need to h...
# general
Hi all, currently our team encountered a need to have “multi stage deployment” from pulumi. An example user flow is to run pulumi up first to setup initial infra, then do some development on the initial infra, and then there is a need to deploy the newly developed resources on the initial infra. The current workaround is to have flags, and manually switch them on or off. Is there a better flow (e.g. setup a separate pulumi project just for the last deployment stage)?
If the resources have different lifecycles (i.e., one needs to be deployed more frequently or on a different schedule than others), then I’d probably put those resources in a separate project and use stack references as needed.
What about to use 2 stacks in the same project instead of 2 different projects?
That’s possible too. In general I’d recommend using stacks to model different environments for your infrastructure.
I liked the stack reference idea, because in this case the second round of deployment is running on top of the first round of deployment, and second round runs more often too.
Thanks all for the suggestions!
Happy to help, let us know if we can help further!