Q: Does anyone version their Pulumi config? I hav...
# general
Q: Does anyone version their Pulumi config? I have a breaking change I’d like to make and want to use it for new stacks, but not necessarily existing ones. Really what I want is the ability to branch my config… Example reason for a breaking change: switching providers, which would replace all resources in the stack. One option I considered is adding a
parameter to my config and splitting my Pulumi code into
. This would involve a lot of duplication. Any thoughts on a more elegant solution?
Do you mean your Pulumi.<stack>.yaml? Yes, that goes into git along with everything else. Though since you're talking about provider versions, that's defined by your yarn.lock / package-lock.json (or equivalent for your language). You can choose to version that too, there are arguments both ways on that one.