Skip to main content
Pulumi logo Pulumi logo
  1. Docs
  2. Reference
  3. REST API Docs
  4. Schema
  5. UpdateTeamRequest

UpdateTeamRequest

    UpdateTeamRequest modifies a team.

    Properties

    • newDisplayName string optional
      The new display name for the team.
    • newDescription string optional
      The new description for the team.
    • memberAction enum optional
      MemberAction is the action to perform.
      Values: add, remove, promote, demote
    • member string optional
      Member to be added or removed based on MemberAction.
    • addStackPermission TeamStackPermission optional
      A stack permission to add to the team.
    • projectName string required
      The project containing the stack.
    • stackName string required
      The stack within the project.
    • permission enum required
      The permission level the team has on this stack (e.g., read, write, admin). On editStackPermission, set to “none” to remove the stack from the team. addStackPermission ignores “none” — including an omitted permission, which reads as “none” — and stores nothing: adding is how a grant is created, and removeStack is how one is revoked.
      Values:
      0 — None
      StackPermissionNone provides no access.
      101 — Read
      StackPermissionRead provides read-only access, including the ability to decrypt encrypted configuration secrets stored in the service.
      102 — Write
      StackPermissionWrite provides read/write access to a stack.
      103 — Admin
      StackPermissionAdmin provides admin-level access to the stack. For example, being able to run pulumi destroy or delete the stack.
      104 — Creator
      StackPermissionCreator identifies the user who created the stack. It confers the same access as StackPermissionAdmin.
    • permissionSetName string optional
      Display name of the permission set for this stack, when available. Enables read-only entity access UI without requiring RoleRead.
    • editStackPermission TeamStackPermission optional
      A stack permission to edit on the team.
    • projectName string required
      The project containing the stack.
    • stackName string required
      The stack within the project.
    • permission enum required
      The permission level the team has on this stack (e.g., read, write, admin). On editStackPermission, set to “none” to remove the stack from the team. addStackPermission ignores “none” — including an omitted permission, which reads as “none” — and stores nothing: adding is how a grant is created, and removeStack is how one is revoked.
      Values:
      0 — None
      StackPermissionNone provides no access.
      101 — Read
      StackPermissionRead provides read-only access, including the ability to decrypt encrypted configuration secrets stored in the service.
      102 — Write
      StackPermissionWrite provides read/write access to a stack.
      103 — Admin
      StackPermissionAdmin provides admin-level access to the stack. For example, being able to run pulumi destroy or delete the stack.
      104 — Creator
      StackPermissionCreator identifies the user who created the stack. It confers the same access as StackPermissionAdmin.
    • permissionSetName string optional
      Display name of the permission set for this stack, when available. Enables read-only entity access UI without requiring RoleRead.
    • removeStack RemoveStackIdentifier optional
      A stack to remove from the team.
    • projectName string required
      The name of the project containing the stack.
    • stackName string required
      The name of the stack to remove.
    • addEnvironmentPermission TeamEnvironmentSettings optional
      An environment permission to add to the team.
    • projectName string required
      The project containing the environment.
    • envName string required
      The environment within the project.
    • permission enum required
      The permission level the team has on this environment. On editEnvironmentPermission, set to “none” to remove the environment from the team. addEnvironmentPermission ignores “none” and stores nothing: adding is how a grant is created, and removeEnvironment is how one is revoked.
      Values: none, read, open, write, admin
    • maxOpenDuration string optional
      The maximum duration an environment session can remain open, as a Go duration string (e.g. “1h30m”).
    • permissionSetName string optional
      Display name of the permission set for this environment, when available. Enables read-only entity access UI without requiring RoleRead.
    • editEnvironmentPermission TeamEnvironmentSettings optional
      An environment permission to edit on the team.
    • projectName string required
      The project containing the environment.
    • envName string required
      The environment within the project.
    • permission enum required
      The permission level the team has on this environment. On editEnvironmentPermission, set to “none” to remove the environment from the team. addEnvironmentPermission ignores “none” and stores nothing: adding is how a grant is created, and removeEnvironment is how one is revoked.
      Values: none, read, open, write, admin
    • maxOpenDuration string optional
      The maximum duration an environment session can remain open, as a Go duration string (e.g. “1h30m”).
    • permissionSetName string optional
      Display name of the permission set for this environment, when available. Enables read-only entity access UI without requiring RoleRead.
    • removeEnvironment RemoveEnvironmentIdentifier optional
      An environment to remove from the team.
    • projectName string required
      The name of the project containing the environment.
    • envName string required
      The name of the environment to remove.

      The infrastructure as code platform for any cloud.