handsome-lizard-2724
04/08/2019, 8:46 PMlemon-spoon-91807
04/08/2019, 8:52 PMhandsome-lizard-2724
04/08/2019, 9:28 PMlemon-spoon-91807
04/08/2019, 9:30 PMcolossal-beach-47527
04/08/2019, 9:31 PMpulumi up
on a stack you don’t have permissions to access, e.g. one in a different Pulumi organization, you’d see a 404 instead of a 403. However, in this situation it doesn’t seem like that is the case.pulumi stack ls
, pulumi whoami
and pulumi up
show?handsome-lizard-2724
04/08/2019, 9:35 PMpulumi up
2. I selected the stack from the stack selection
3. I got a 404 stack not found
4. Tried pulumi up -s <stack name>'
5. Got 404
6. pulumi stack select
7. Picked the stack
8. pulumi up
9. 404
10. pulumi.com...see the stack
11. cry
Then a team member added me to the AWS IAM role that granted access to the related AWS resources. Now all things pulumi xxx
work as expected.colossal-beach-47527
04/08/2019, 9:48 PMThen a team member added me to the AWS IAM role that granted access to the related AWS resources. Now all things
Copy codepulumi xxx
work as expected.That’s definitely some surprising behavior 😛 , and almost certainly a bug somewhere in the
pulumi
CLI. Could you share with me the name of the Pulumi stack that you got these errors on, but were eventually able to successfully run pulumi up
? That will allow me to query our backend API logs, to see what response codes were sent to the CLI tool.
I suspect the problem is actually in the pulumi
tool itself, since any error messages relating to resource management (e.g. AWS IAM creds) don’t interact with the Pulumi Service’s API.handsome-lizard-2724
04/08/2019, 10:02 PMcolossal-beach-47527
04/08/2019, 10:09 PM404
from the CLI.
- After you were added to the team and added WRITE
permission to the stack, you were able to update it like intended.handsome-lizard-2724
04/08/2019, 10:15 PM