lively-vr-73939
03/31/2022, 1:56 PMS3
bucket as the backend. I believe the Pulumi.<stack>.yaml
should not be committed (pls correct me if I'm wrong). May I please know the recommended way of setting the configs? Should I set the each config from environment variable using pulumi config set/set-all
command? If so How should I set the secretsprovider
and the encryptedkey
? Or can I retrieve those configs from backend?echoing-dinner-19531
03/31/2022, 2:08 PMI believe theYou should commit it if others are using the same stack.should not be committedPulumi.<stack>.yaml
Should I set the each config from environment variable usingIf you've just got an envvar that controls things you could just read the envvar in your pulumi program, it doesn't have to go via config.command?pulumi config set/set-all
If so How should I set theThose should normally be set for you on stack initialisation.and thesecretsprovider
?encryptedkey
lively-vr-73939
03/31/2022, 2:12 PMworried-xylophone-86184
04/14/2022, 10:34 AMPulumi.<STACK>.yaml
file from another location say S3 bucket or Github?
Something like this perhaps
pulumi preview -s STACK_NAME --config-file <s3://pulumi-backend-aws/stack_files/Pulumi.STACK_NAME.yaml>
echoing-dinner-19531
04/14/2022, 10:37 AMstackConfigDir
option in Pulumi.yaml (https://www.pulumi.com/docs/reference/pulumi-yaml/) but that's just a folder path (and the docs do say relative to Pulumi.yaml, although I suspect an absolute path there would happen to work)worried-xylophone-86184
04/14/2022, 10:40 AM--show-config
available with both pulumi up and pulumi preview. So saving the staet file should suffice.
Thanks for the stackConfigDir advice too Fraser 🙂 I am going to use that too in my projectlively-vr-73939
04/17/2022, 1:02 AMencryptionSalt
value visible in Pulumi.<STACK>.yaml
file in a public git repository.lively-vr-73939
04/19/2022, 5:38 AM