Example command:
az devops invoke --area distributedtask --resource jobrequests --route-parameters poolId={myPoolId} --organization {myOrg} --query-parameters `$top=1will translation to the following URL:
{myOrg}/_apis/distributedtask/pools/{myPoolId}/jobrequests?$top=1
This works as expected and returns a JSON response to the console. The problem is that, if I need to get to the next page, the server sends the continuation token as a header instead of embedded in the JSON body response and az devops invoke doesn't expose response headers at all, that I can see.
Example command:
az devops invoke --area distributedtask --resource jobrequests --route-parameters poolId={myPoolId} --organization {myOrg} --query-parameters `$top=1will translation to the following URL:
This works as expected and returns a JSON response to the console. The problem is that, if I need to get to the next page, the server sends the continuation token as a header instead of embedded in the JSON body response and az devops invoke doesn't expose response headers at all, that I can see.