hi Pulumi team :wave: reposting this question, hopefully we'll get some response :crossed_fingers: ...
s
hi Pulumi team 👋 reposting this question, hopefully we'll get some response 🤞 we have transferred our stack from individual to organization. We generated our access token from individual and on redeployment, our stack was not updated in organization, rather it created a new stack in individual. Do the access token needs to be generated from organization? We just want to have a clear understanding because based on this doc it says, "_Members are able to view and edit stacks they have access to and view members and teams."_
g
Hi Mau 👋 ! I just tried this to confirm the mechanics. I transferred a stack from my individual account to another account where I have admin permissions. In my CLI upon
pulumi up
it prompted me to select a stack with the new destination already populated as one of the options. After
pulumi up
, resources were created in the new destination. The CLI steps were done with an individual token not a team or org token. Access to the stack in the new destination needs to be explicitly set using the Team Access option in the stack settings. I hope this is clarifying. https://www.pulumi.com/docs/support/faq/#how-do-i-migrate-stacks-from-an-individual-account-to-an-organization-account
🙏 1
👀 1