Add TeamEnvironmentPermission resource

[ekkohdev]

Hello!

• Vote on this issue by adding a 👍 reaction
• If you want to implement this feature, comment to let us know (we'll work with you on design, scheduling, etc.)

Issue details

With the introduction of Pulumi ESC it would be very useful for this provider to be able to create/delete an Environment, as well as grant Environment permissions to Teams. We use a centralised GitHub repo and this provider to provide a self-service way for teams to manage things like Pulumi Cloud Teams and Stack Permissions for those Teams. We would like to do the same for Environments.

There is a wider issue (pulumi/esc#63) describing the ability to manage the desired state of an Environment from this provider. This request however is simply to manage the existence of the Environment and Team permissions for it, not the state within it.

Examples

const env = new pulumiservice.Environment("team-owned-environment", {
    organization: "acme-corp",
    name: "team-owned-environment",
});

new pulumiservice.TeamEnvironmentPermission(
    "team-a-team-owned-environment,
    {
        organization: "acme-corp",
        team: "team-a",
        environment: "team-owned-environment",
        permission: pulumiservice.TeamEnvironmentPermissionScope["Write"],
    },
    { dependsOn: env },
);

Affected area/feature

• Pulumi ESC
• Pulumi Cloud Service

[komalali]

Renaming this issue to specifically be about TeamEnvironmentPermission - tracking the Environment resource in #225

[IaroslavTitov]

Resolved in #279
Closing issue

Environment resource will be added in #271, as part of another issue