Related command
az devops security group membership list
Is your feature request related to a problem? Please describe.
Yes. Currently a certain group in our organization has more than 500 members in a security group. When we use this command to get its members we get the error "ERROR: TF400049: The request was aborted because it contained too many requested items <more than 500>, maximum allowed is 500." As there is no option for providing a continuation token (nor is it provided), we cannot get members for this group.
Describe the solution you'd like
- Add a continuation token to the response of
az devops security group membership list if a group has more than 500 members.
- Add a
--continuation-token argument to provide the continuation token returned to paginate through the response. The implementation could be similar to the --continuation-token argument in commands like az devops project list.
Describe alternatives you've considered
We eventually achieved our goals using the Azure DevOps REST API, however that solution was harder to implement than the solution that I propose here.
Related command
az devops security group membership listIs your feature request related to a problem? Please describe.
Yes. Currently a certain group in our organization has more than 500 members in a security group. When we use this command to get its members we get the error "ERROR: TF400049: The request was aborted because it contained too many requested items <more than 500>, maximum allowed is 500." As there is no option for providing a continuation token (nor is it provided), we cannot get members for this group.
Describe the solution you'd like
az devops security group membership listif a group has more than 500 members.--continuation-tokenargument to provide the continuation token returned to paginate through the response. The implementation could be similar to the--continuation-tokenargument in commands likeaz devops project list.Describe alternatives you've considered
We eventually achieved our goals using the Azure DevOps REST API, however that solution was harder to implement than the solution that I propose here.