Open emilhvid opened 2 years ago
I can reproduce with azure devops version 1.0.1. The problem might be that the resourceArea
API query returns two templates for the invoke
request:
{
"id": "72c7ddf8-2cdc-4f60-90cd-ab71c14a399b",
"area": "wit",
"resourceName": "workItems",
"routeTemplate": "{project}/_apis/{area}/{resource}/{id}",
"resourceVersion": 3,
"minVersion": "1.0",
"maxVersion": "7.2",
"releasedVersion": "7.1"
}
{
"id": "62d3d110-0047-428c-ad3c-4fe872c91c74",
"area": "wit",
"resourceName": "workItems",
"routeTemplate": "{project}/_apis/{area}/{resource}/${type}",
"resourceVersion": 3,
"minVersion": "1.0",
"maxVersion": "7.2",
"releasedVersion": "7.1"
},
There's probably an overlap with az devops
trying to find the correct URL. az devops invoke --area wit --resource workItems --route-parameters type=1234
gives me a different error:
The controller for path '/_apis/wit/workItems/$1234' was not found or does not implement IController. Operation returned a 404 status code.
This is autogenerated. Please review and update as needed.
Describe the bug
Command Name
az devops invoke Extension Name: azure-devops. Version: 0.23.0.
Errors:
To Reproduce:
Steps to reproduce the behavior. Note that argument values have been redacted, as they may contain sensitive information.
az devops invoke --detect false --area wit --resource workItems --route-parameters project=<project> id=<id>
Expected Behavior
Output a workitem
Environment Summary
Additional Context