glamorous-cpu-85849
04/22/2021, 1:16 PMPulumi.<stack_name>.yaml
file, I'm not sure what the best solution is here. Example: multiple stacks considered 'dev' in the same environment. Aside from having random char generation and ending up with Pulumi.8dnfa2.yaml
which is not very helpful for human operators, what are the other options? Any support for nested folders inside project? Inheritance for Pulumi.<stack_name>.yaml
? Some kind of hack or wrapper? Organize projects and stacks differently? Appreciate insight here!bored-oyster-3147
04/22/2021, 1:17 PMdev-networking
, dev-storage
, dev-api
etcred-match-15116
04/22/2021, 6:43 PMPulumi.dev-[user].yaml
glamorous-cpu-85849
04/22/2021, 11:11 PMlittle-cartoon-10569
04/22/2021, 11:40 PMbored-oyster-3147
04/23/2021, 12:14 AMpulumi config cp
so you could setup a stack as your "schema" stack and put the config in that and then make part of your process that after you create the new stack you copy the config from the schema stack.
Or you could use Automation API to manage your stacks. Then like @little-cartoon-10569 said spawning a new replica stack and moving config around would just be programmaticglamorous-cpu-85849
04/23/2021, 12:43 AM