Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
[Bug] az devops security group create fails with "API resource location … is not registered on …"
See original GitHub issueDescribe the bug
When running any az devops security group * command against Azure DevOps Server 2020 (e.g. az devops security group create or list) it fails with the error message:
API resource location 048aee0a-7072-4cde-ab73-7af77b1e0b4e is not registered <Collection_URL>
To Reproduce
Versions: azure-cli 2.19.1 azure-devops: 0.18.0 Azure DevOps Server: 2020.RTW
Steps to reproduce the behavior:
- Set PAT to
AZURE_DEVOPS_EXT_PATenvironment variable - Run command:
az devops project list --org http://server:8080/tfs/collectionruns fine - Run command:
az devops security group list --org http://server:8080/tfs/collection --scope organizationfails - See error
Expected behavior It should list the security groups.
Screenshots
Debug logs Available upon request (contains private URLs)
Issue Analytics
- State:
- Created 3 years ago
- Reactions:1
- Comments:10 (4 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
What we probably need is some documentation which CLI commands are compatible with DevOps Server 2020 and which are not.
I am exactly facing same issue, and still did not find the solution for this issue. My version: “azure-cli”: “2.20.0”, “azure-cli-core”: “2.20.0”, “azure-cli-telemetry”: “1.0.6”, “extensions”: { “azure-devops”: “0.18.0”
Azure DevOps Server Version Dev18.M170.8