Repository navigation
Conversation
Lists the users of the tenant, with role, teams, what manages them and last login, and removes a user from the tenant. Both call the platform's new GET /api/users and DELETE /api/users/{username}; the client is regenerated from the dev spec, which has them.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds commands for the platform's two new user endpoints.
steadybit user list [--query <text>] [-t json|yaml](GET /api/users): a table of username, name, email, role, teams, what manages the user (SCIM, or Steadybit) and last login. With-tor--jqit prints the platform's items as they are.steadybit user delete --username <username> [--yes](DELETE /api/users/{username}): removes a user from the tenant and asks for confirmation on a terminal. A user who is not a member gets its own message. Every other refusal shows the platform's reason: admins can't remove themselves, and users managed by SCIM or an LDAP sync are removed there.Both need an admin access token.
openapi/platform-api.jsonandapi/platform.gen.goare refreshed from the dev spec, which also brings in other dev-only API changes, such as new fields in the experiment list.Merge after the platform release that brings these endpoints to prod. Until then,
api-compatibilityfails: it builds against the live prod spec, which does not havegetUsers/removeUseryet.Platform: steadybit/platform#2128 (the endpoints) and steadybit/platform#2135 (
managedBy). Card: https://steadybitgmbh.kanbanize.com/ctrl_board/2/cards/13444