sparse-intern-71089
11/06/2023, 7:41 AMsalmon-account-74572
11/06/2023, 1:36 PMbreezy-television-71515
11/06/2023, 4:08 PMsalmon-account-74572
11/06/2023, 8:29 PMpulumi config set <key> <value>
to write values into the stack configuration file (Pulumi.<stack>.yaml
), you create an ESC environment and store the configuration values there. You can then reference that ESC environment from multiple stacks; changing the ESC environment will then change it for all stacks that reference it (the change will take effect on the next pulumi up
).
ESC doesn’t fundamentally change any of the guidelines or recommendations around when to use multiple stacks---it just makes using configuration across multiple stacks potentially MUCH easier.
As for maintaining versions of a provider, the versions are specified using whatever language-specific mechanisms are in place. For Python, there’s a requirements.txt
that specifies the versions, and pulumi new
will automatically create a virtual environment when a Python template is selected. So, yes---using virtual environments and installing the versions specified in requirements.txt
(which would be checked into version control) is the right approach.breezy-television-71515
11/07/2023, 7:10 AMsalmon-account-74572
11/07/2023, 4:13 PM