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.

Pulumi Community

I'm getting an weird error when run `pulumi install` command:
```error: failed to download plugin: esc-sdk-0.10.4: failed to download plugin: esc-sdk-0.10.4: 403 HTTP error fetching plugin from <https://get.pulumi.com/releases/plugins/pulumi-resource-esc-sdk-v0.10.4-darwin-arm64.tar.gz>```


looks like AccessDenied issue:
```This XML file does not appear to have any style information associated with it. The document tree is shown below.
&lt;Error&gt;
&lt;Code&gt;AccessDenied&lt;/Code&gt;
&lt;Message&gt;Access Denied&lt;/Message&gt;
&lt;RequestId&gt;08QNTN7KW0XR13YK&lt;/RequestId&gt;
&lt;HostId&gt;Z/3VwNn0jTgZgLSHaetYjA/yqTNvLBgYdjVwWlO2kXXqtqFv1Y5wlpEZb3DpIEczZPr0VkT4XRg=&lt;/HostId&gt;
&lt;/Error&gt;```

I created an issue for that:
<https://github.com/pulumi/esc-sdk/issues/57>

hey <@U01FHMA71BK> sorry to intrude - just stumbled on this and your comment "If we could have RBAC for Pulumi, ESC like Pulumi Stacks would be amazing. We needed to keep developers out of ESC until we could have more granulation in the access control." - would this help at all <https://www.pulumi.com/docs/esc/environments/access-control/>

<@U076R8HUSSU>, thank you very much for sharing this document. Let me share a little bit about my environment. Our environment has some requirements such as cloud agnostic, which requires more stacks and credentials than the average use case, in addition to also requiring a series of audits and controls, which requires that the default access policy be to not allow access. When we integrated Pulumi Cloud with our directory, it was great, because user management is based on groups that we linked to the Pulumi Cloud Teams resource. We can currently authorize a group of users to have access to stacks based on tags, projects, providers, etc. This flexibility allows us to define tags for stacks and environments as well, but ESC does not yet have this feature, which I called RBCA, because in Kubernetes we can define privileges in the same way. Sorry for the long explanation, but I felt the need to share the context. Any ideas are always very welcome.

thanks for the explanation! I think I understand now - you're waiting on pulumiservice to support this e.g. <https://github.com/pulumi/pulumi-pulumiservice/issues/404> to be completed then?

<@U076R8HUSSU> I added a comment there. Thanks