refactor: update user and user group queries to use machinery #304
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.
Checklist
This updates some user and group queries to use machinery.
Notable changes include
list users
and replaces it withlist group-users
. This command works best if provided the group name, but if not provided will attempt to get all groups and members. Not currently recommended for large lagoon installations.list user-groups
which if provided an email address will return the groups the user is in.list all-users
which will return all users within Lagoon (even those that are not in any groups) but does not return any information about the groups the user is in, use thelist user-groups
command for specific users.All of these commands are RBAC wrapped, if you use these commands and get a permission denied, this is because you do not have permission to do the requested action.
list user-groups
is scoped to self, and platform. You can't view another users groups, only your own.list all-users
is platform onlylist group-users
is scoped to groups you are a member of for a specific group, or platform for all groupsChangelog Entry
Requires
Closes
closes #271