Repository navigation
Conversation
…mmands MeshWorkspaceUserGroupClient covers create, read, update, delete and list of meshWorkspaceUserGroup v1, addressed by workspace.group. MeshUserClient reads a meshUser v2 by username and lists users by uuid, username, email, euid, workspace, workspace role or project. Both are new fields of client.Client, so the Terraform provider's mocks keep compiling, and client.New registers both with Raw. The group listing documents no sort parameter, so it keeps meshStack's own order. meshstack user list lists the users with a role in the workspace, and meshstack workspaceusergroup list (alias wug) the groups the workspace owns. meshStack answers 400 to a group listing that filters by workspace and username at once, so --username lists the user's groups in every workspace the credential can access. The workspaceUserGroupIdentifier filter of the user listing is left out: the API docs do not say whether it takes the group name or workspace.group. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
grubmeshi
requested changes
Nov 19, 2026
| "github.com/meshcloud/meshstack-cli/cmd/internal" | ||
| ) | ||
|
|
||
| func newList() *cobra.Command { |
Collaborator
There was a problem hiding this comment.
d: would it be enough for now adding the client/ package changes only and the corresponding TF provider resources for now? I'm a bit reluctant to extend the CLI api here in one go, in particular considering that meshstack api is already there to talk to that public api without a dedicated set of CLI list commands for now?
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
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.
…mmands
MeshWorkspaceUserGroupClient covers create, read, update, delete and list of meshWorkspaceUserGroup v1, addressed by workspace.group. MeshUserClient reads a meshUser v2 by username and lists users by uuid, username, email, euid, workspace, workspace role or project. Both are new fields of client.Client, so the Terraform provider's mocks keep compiling, and client.New registers both with Raw. The group listing documents no sort parameter, so it keeps meshStack's own order.
meshstack user list lists the users with a role in the workspace, and meshstack workspaceusergroup list (alias wug) the groups the workspace owns. meshStack answers 400 to a group listing that filters by workspace and username at once, so --username lists the user's groups in every workspace the credential can access.
The workspaceUserGroupIdentifier filter of the user listing is left out: the API docs do not say whether it takes the group name or workspace.group.