This message was deleted.

sparse-intern-71089

07/20/2022, 8:43 PM

This message was deleted.

alert-spoon-97538

07/20/2022, 8:44 PM

The reason I even started going down this path was after configuring the AWS cli I spit out the AWS config and I'm currently seeing the following ....

alert-spoon-97538

07/20/2022, 8:44 PM

Copy code

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

07/20/2022, 8:46 PM

@alert-spoon-97538 the profile might be set inside the stack configuration, if you run a successful up with a config setting it gets passed to the stack config

alert-spoon-97538

07/20/2022, 9:07 PM

I tried running

pulumi config rm aws:profile

right before

pulumi up

to see if that changed anything and it did not

little-cartoon-10569

07/20/2022, 9:12 PM

Is it specified in code? When you construct the provider? Search for all provider constructors.

alert-spoon-97538

07/20/2022, 9:14 PM

provider

isn't used in the code at all

little-cartoon-10569

07/20/2022, 9:29 PM

Have you output the value of AWS_PROFILE as seen by the CI job? Maybe that'll give you a hint where the value is coming from. Maybe an earlier step / action is setting it?

alert-spoon-97538

07/20/2022, 9:44 PM

good idea

alert-spoon-97538

07/20/2022, 9:56 PM

nope

26 Views

Open in Slack

Previous Next

Pulumi Community

No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.