Teams

Modify an existing team.

put/v2/organizations/{organization}/teams/{team}

Request

Base URL
https://docs.tetrate.io (the document declares no server; this is the origin it was published from)
Auth
none declared
TypeScript
https://skmtc.dev/tetrate/apis/tetrate-service-bridge-api/docs/v2/organizations/:organization/teams/:team/put.ts
A function with typed inputs. Its response is checked against the schema.

Path parameters

organizationstring required

Organization name.

teamstring required

Team name.

Request body

descriptionstring

displayNamestring

etagstring

membersstring[]

List of members under the team. The elements of this list are the FQNs of the team members. Team members can be users, service accounts or other teams.

sourceType'INVALID' | 'LDAP' | 'LOCAL' | 'AZURE' | 'MANUAL'

SourceType describes where teams come from. Teams can be synchronized from the Identity Provider but can also be manually created using the Team API to create convenient groupings of users and other teams in order to configure fine-grained permissions in the Management Plane.

LDAP: LDAP is used for users and teams that are automatically synchronized from LDAP.
LOCAL: LOCAL is used for local teams that are manually created using the TSB Team API and do not exist in the Identity Provider. Deprecated. This value is deprecated and will be removed in future releases. Use 'MANUAL' instead.
AZURE: AZURE is used for users synchronized from an Azure Active Directory.
MANUAL: MANUAL is used for users and teams that exist in the Identity Provider that have been manually populated. MANUAL users are deprecated and Service Accounts should be used instead. Support for MANUAL users will be removed in future versions.

Response

A successful response.

fqnstring