-
-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Doesn't handle other Azure Clouds #55
Comments
2019-09-16T14:56:09.8663413Z ##[section]Starting: Key Vault ARM Outputs |
Adding some more logs: 2019-09-26T16:26:12.6846560Z Logging in using ApplicationTokenCredentials, authScheme is 'ServicePrincipal' If you're using some kind of detection on where Azure DevOps is hosted, the service is always hosted in Commercial (versus Azure US Government). I don't know about China, though. However, the correct cloud/resourcemanagerurl should be available via the Service Connection/context. |
I also encounter this issue when deploying resources in China Azure. Hope we can fix this issue. |
Closed with #75 |
Update 5.3 has so far proven successful in using the ARM Outputs extension with the Azure China environment service connections. |
Re-opening #38. Extension does not work for Azure China or other Azure clouds. ResourceManagementClient is making calls to https://management.azure.com/ baseUri by default. Made changes and tested with private extension in personal DevOps org. See PR #54 referenced below.
The text was updated successfully, but these errors were encountered: