alert-spoon-97538
07/20/2022, 8:43 PMA Profile was specified along with the environment variables "AWS_ACCESS_KEY_ID" and "AWS_SECRET_ACCESS_KEY". The Profile is now used instead of the environment variable credentials. This may lead to unexpected behavior.
I do set the config aws:profile locally and I tried removing that in the CI prior to up
and re-adding it after though that didn't change the log line above. Is this an issue or a red herring?Name Value Type Location
---- ----- ---- --------
profile <not set> None None
access_key ****************ISEZ env
secret_key ****************0alB env
region us-east-1 env ['AWS_REGION', 'AWS_DEFAULT_REGION']
billowy-army-68599
alert-spoon-97538
07/20/2022, 9:07 PMpulumi config rm aws:profile
right before pulumi up
to see if that changed anything and it did notlittle-cartoon-10569
07/20/2022, 9:12 PMalert-spoon-97538
07/20/2022, 9:14 PMprovider
isn't used in the code at alllittle-cartoon-10569
07/20/2022, 9:29 PMalert-spoon-97538
07/20/2022, 9:44 PM