UpdateTeamRequest
UpdateTeamRequest modifies a team.
Properties
newDisplayNamestring optionalThe new display name for the team.newDescriptionstring optionalThe new description for the team.memberActionenum optionalMemberAction is the action to perform.Values:add,remove,promote,demotememberstring optionalMember to be added or removed based on MemberAction.- A stack permission to add to the team.
- ↳
projectNamestring requiredThe project containing the stack. - ↳
stackNamestring requiredThe stack within the project. - ↳
permissionenum requiredThe 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 destroyor delete the stack. 104— Creator- StackPermissionCreator identifies the user who created the stack. It confers the same access as StackPermissionAdmin.
- ↳
permissionSetNamestring optionalDisplay name of the permission set for this stack, when available. Enables read-only entity access UI without requiring RoleRead. - A stack permission to edit on the team.
- ↳
projectNamestring requiredThe project containing the stack. - ↳
stackNamestring requiredThe stack within the project. - ↳
permissionenum requiredThe 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 destroyor delete the stack. 104— Creator- StackPermissionCreator identifies the user who created the stack. It confers the same access as StackPermissionAdmin.
- ↳
permissionSetNamestring optionalDisplay name of the permission set for this stack, when available. Enables read-only entity access UI without requiring RoleRead. - A stack to remove from the team.
- ↳
projectNamestring requiredThe name of the project containing the stack. - ↳
stackNamestring requiredThe name of the stack to remove. - An environment permission to add to the team.
- ↳
projectNamestring requiredThe project containing the environment. - ↳
envNamestring requiredThe environment within the project. - ↳
permissionenum requiredThe 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 - ↳
maxOpenDurationstring optionalThe maximum duration an environment session can remain open, as a Go duration string (e.g. “1h30m”). - ↳
permissionSetNamestring optionalDisplay name of the permission set for this environment, when available. Enables read-only entity access UI without requiring RoleRead. - An environment permission to edit on the team.
- ↳
projectNamestring requiredThe project containing the environment. - ↳
envNamestring requiredThe environment within the project. - ↳
permissionenum requiredThe 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 - ↳
maxOpenDurationstring optionalThe maximum duration an environment session can remain open, as a Go duration string (e.g. “1h30m”). - ↳
permissionSetNamestring optionalDisplay name of the permission set for this environment, when available. Enables read-only entity access UI without requiring RoleRead. - An environment to remove from the team.
- ↳
projectNamestring requiredThe name of the project containing the environment. - ↳
envNamestring requiredThe name of the environment to remove.