I have a personal account with Pulumi and I'm added to an organization. I created a project/stack and created it from my local machine using
pulumi up
. Then in the portal, I transfered the project/stack to my organization. Now when I pulumi up/destroy/etc, it's tracked in the organization's portal. Perfect.
I then created a Pulumi Access Token (from my personal account since I can't do that through the organization), and used it with a GitHub Action. The GitHub Action works, but now there's a new copy of the project/stack being tracked in my personal account. The project/stack in the organization is still there but doesn't know anything about trying to be updated by the GitHub Action.
Is there a way to force the GitHub Action to use the organization account? Or is there a way to make a pulumi access token linked to the organization account instead of my personal account?
b
bored-table-20691
02/17/2022, 6:32 PM
I think it’ll work if you specify the fully qualified name of the stack, e.g.
your_org/your_stack
bored-table-20691
02/17/2022, 6:33 PM
Locally if you do
pulumi stack ls
you’ll see stacks in your personal account as
<stack>
and in your org account as
<org>/<stack>
m
modern-quill-17695
02/17/2022, 6:43 PM
Perfect, that fixed it for me. Thank you so much!
b
bored-table-20691
02/17/2022, 6:48 PM
No problem - this wasn’t obvious, and I was confused as well the first time 🙂
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.