https://pulumi.com
Join Slack
This message was deleted.
# general
s
This message was deleted.
g
How have you provided your AWS credentials?
c
yea, i have run both 
pulumi config set aws:profile the-profile
and 
AWS_PROFILE=the-profile pulumi up
and neither work
i have 
aws-cli
installed with an 
~/.aws/credentials
file with several profiles fwiw
oh interesting. it defaulted to use the value in 
Pulumi.dev.yml
, so this was pointing to the wrong profile that didn’t have permissions to create a bucket.
c
it defaulted to use the value in 
Pulumi.dev.yml
, so this was pointing to the wrong profile that didn’t have permissions to create a bucket.
It should shouldn’t “default” to a specific stack as far as I know. It might be that that was the last stack you used? I believe if you run 
pulumi stack select <stack name>
it should change the active stack. You can see the active stack by running 
pulumi stack ls
in the directory where your stack config files are, and you should see a 
*
next to the currently selected one. EDIT: Sorry. I had a typo in my message above. I actually meant to type, it shouldn’t default to a specific stack.
Were you passing the 
-s
flag to your 
pulumi up
command previously? If so, that wouldn’t change the active stack, just runs the command with that stack’s config, as though it were the active stack.
c
i did not use the 
-s
flag, this was my first attempt using the getting started workflow.
g
What was set in your 
Pulumi.dev.yaml
?
c
the wrong AWS profile that did not have the correct permissions to execute
3 Views
Open in Slack
PreviousNext
Powered by

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.

Powered by