gentle-exabyte-9924406/07/2023, 3:41 PM
clever-sunset-7658506/08/2023, 3:29 PM
file. Especially, if you are running a bunch of
commands to set stack config properties. For Azure, you are required to set some provider config by default for every stack, so at the very least you'll have at least one config per stack.
Technically, there is a way to get around the error you are referring to. Instead of running
pulumi config set ...
you could run
pulumi stack init
pulumi stack select <stack name> -c
will cause the CLI to create the stack if it doesn't exist before selecting it. But as I mentioned above, you should check-in the stack config file as a best practice, unless you also intend to destroy the stack completely in your pipeline. Sort of like an ephemeral stack, in which case, you don't need to create anything ahead of time and simply use the
gentle-exabyte-9924406/12/2023, 5:41 PM
clever-sunset-7658506/12/2023, 5:43 PM
polite-sandwich-6854706/16/2023, 11:45 AM