Resources.CheckExistenceByIdAsync() issue
See original GitHub issueI noticed ‘Bad request’ errors while calling Resources.CheckExistenceByIdAsync(resourceId, apiVersion)
.
Digging through the actual request using Postman I see it does a HEAD request to https://management.azure.com//subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Storage/storageAccounts/{resourceName}?api-version=2018-07-01
and that returns after >40 seconds with ‘503 - service unavailable’.
Issue Analytics
- State:
- Created 5 years ago
- Comments:14 (7 by maintainers)
Top Results From Across the Web
CheckExistenceByID and CheckExistence always ...
MethodGet should resolve he issue. I've tested this using the Azure Rest API and can only get the resource when the method is...
Read more >Check Existence - REST API (Azure Resource Management)
Learn more about Resource Management service - Checks whether a resource exists.
Read more >Status of asynchronous operations - Azure
Describes how to track asynchronous operations in Azure. It shows the values you use to get the status of a long-running operation.
Read more >// , Packer 1.2.4 - Azure Resource Not Found
The service provider which I'm using for this has owner permissions on the resource group with the super creative name packerresourcegroup. Which means...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@DeepakMohanSingh Many service does not support this
HEAD
http method. Hence it fails. It would require fix from service.Hi @snaheth, I don’t think the fact that out of a hundred or two RPs only 4 support HEAD is a good argument not to support it. More practically speaking - make them to support it.
Also your words directly contradict the public documentation at https://docs.microsoft.com/en-us/rest/api/resources/resources/check-existence
However, it’s not you. It’s the documentation that must be fixed asap.