Context: #6088
TL;DR:
Currently, we have a bunch of entra group user commands. These commands work with all kinds of groups, like security groups. Security groups can be nested (you can put a security group into a security group). Currently, our commands don't support this. For example, if you run entra group user list, the command only returns users, no nested groups, or whatever.
To better reflect what the command does, we should rename all entra group user ... commands to entra group member ....
To do:
|
const expandParam = fieldExpand.length > 0 ? `&$expand=${fieldExpand}` : ''; |
|
const selectParam = allSelectProperties.filter(item => !item.includes('/')); |
|
const endpoint: string = `${this.resource}/v1.0/groups/${groupId}/${role}/microsoft.graph.user?$select=${selectParam}${expandParam}`; |
Context: #6088
TL;DR:
Currently, we have a bunch of
entra group usercommands. These commands work with all kinds of groups, like security groups. Security groups can be nested (you can put a security group into a security group). Currently, our commands don't support this. For example, if you runentra group user list, the command only returns users, no nested groups, or whatever.To better reflect what the command does, we should rename all
entra group user ...commands toentra group member ....To do:
entra group user ...commands toentra group member ....entra group member listcan also output nested groups. This can be done by removing the user filter in the API request. (check code sample below)entra group membercommands need similar changes (probably not)cli-microsoft365/src/m365/entra/commands/group/group-user-list.ts
Lines 182 to 184 in a781c51