Closed tusharshahrs closed 1 year ago
This seems like a potential issue in Pulumi Cloud. From the CLI's perspective, when you run pulumi stack init --teams
, we're just passing along the specified teams to the Pulumi Cloud API endpoint used to create stacks.
Default stack permission controls what access org members have on any given stack within the org by default. The stack creator, whether this be a team or a member has always had write permissions by design.
To enable the feature requested, we have opened: Add support for specifying permission to pulumi stack init --team
Closing as by design. https://github.com/pulumi/pulumi/issues/14326 tracks unblocking the scenario.
What happened?
To define
stack read access
orstack admin access
with thepulumi stack init --teams
commandUsing an
organization token
, we haveNONE
selected.Upon running the command, the default access is
Write
Example
Go to the org:
team-ce
, note this is NOT the personal org.Click on Settings -> Access Management
Change the default from
WRITE
( screen shot below) toNONE
andSave permissions
Create a team via Settings->Teams For example:
tusharinitteams
Next, create an
ORG token
. Settings-> Access Management -> Create token. For example:tushar-testtoken-teams
Save the tokenNow set the token in your cli via PULUMI_ACCESS_TOKEN=
value of tushar-testtoken-teams
Then run pulumi stack init --teams command:
pulumi stack init --teams tusharinitteams
Please enter your desired stack name. To create a stack in an organization, use the formatacmecorp/dev
). stack name (dev):team-ce/shahtdev
Created stack 'team-ce/shahtdev'Stack write permissions
(screen shot below)Output of
pulumi about
pulumi about
Additional context
No response
Contributing
Vote on this issue by adding a 👍 reaction. To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).