sparse-intern-71089
04/21/2021, 2:37 PMbillowy-army-68599
billowy-army-68599
billowy-army-68599
.env
file, and also set them in your stack config. You can specify secret values for the secret access key and encrypt them using the --secret
flagbillowy-army-68599
wooden-student-58350
04/21/2021, 3:06 PMbillowy-army-68599
wooden-student-58350
04/21/2021, 3:53 PM.env
altogether, and I made this work by specifying the bastion creds (for S3 backend) in ~/.aws/credentials
. If I unset those and instead provide the creds in .env
in the project directory, pulumi up
fails with:
error: failed to load checkpoint: blob (key ".pulumi/stacks/development.json") (code=Unknown): NoCredentialProviders: no valid providers in chain. Deprecated.
For verbose messaging see aws.Config.CredentialsChainVerboseErrors
I assumed Pulumi would automatically pull in the env vars from .env
, but it seems Iโm missing a step to get Pulumi to see them.
In the end, I removed the .env
file altogether, and put the dev account aws:accessKey
and aws:secretKey
in the stack config, and Pulumi does the right thing now. Iโm happy for Pulumi to use the bastion creds in the aws credentials file to access the backend & secrets provider.victorious-art-92103
04/21/2021, 6:13 PMvictorious-art-92103
04/21/2021, 6:14 PMvictorious-art-92103
04/21/2021, 6:15 PMvictorious-art-92103
04/21/2021, 6:15 PMbillowy-army-68599
billowy-army-68599
billowy-army-68599
victorious-art-92103
04/21/2021, 6:53 PMvictorious-art-92103
04/21/2021, 6:54 PMSomeResource('name', args, { provider: ... })
over and over again is no fun ๐billowy-army-68599
victorious-art-92103
04/21/2021, 7:10 PMvictorious-art-92103
04/21/2021, 7:11 PMvictorious-art-92103
04/21/2021, 7:11 PMvictorious-art-92103
04/21/2021, 7:39 PMbillowy-army-68599