projectkudu / AzureResourceExplorer

Azure Resource Explorer - a site to explore and manage your ARM resources in style
https://resources.azure.com
Apache License 2.0
199 stars 77 forks source link

NoGETUrl Error message while checking TDE status for a Database #317

Open anweshs-ms opened 3 years ago

anweshs-ms commented 3 years ago

When we are trying to use Azure Resource Explorer to check TDE details for any Azure SQL Database, we are receiving "No GET Url" message. This functionality used to work few weeks ago. Following is the complete Error message:

{ "data": { "error": { "code": "NoRegisteredProviderFound", "message": "No registered resource provider found for location 'eastus' and API version '2017-10-01-preview' for type 'servers/databases/transparentDataEncryption'. The supported api-versions are '2014-04-01, 2014-04-01-preview, 2015-05-01-preview, 2017-03-01-preview, 2019-06-01-preview, 2020-02-02-preview, 2020-08-01-preview, 2020-11-01-preview, 2021-02-01-preview'. The supported locations are 'australiacentral, australiaeast, australiasoutheast, brazilsouth, canadacentral, canadaeast, centralindia, centralus, eastasia, eastus, eastus2, francecentral, germanywestcentral, japaneast, japanwest, jioindiawest, koreacentral, koreasouth, northcentralus, northeurope, norwayeast, southafricanorth, southcentralus, southindia, southeastasia, switzerlandnorth, uaenorth, uksouth, ukwest, westcentralus, westeurope, westindia, westus, westus2, westus3'." } }, "status": 400 }

Repro Steps: Azure Resource Explorer --> Subscriptions --> SubscriptionName --> Resource Groups --> ResourceGroupName --> Providers --> Microsoft.Sql --> Servers --> ServerName --> Databases --> DatabaseName --> transparentDataEncryption --> OperationResults.

Please refer to screenshot for more details.

AzureResourceExplorer_Error

balag0 commented 3 years ago

If this used to work, the error is likely because Microsoft.Sql resource provider has deprecated support for that api version recently.

To fix it , resource explorer would need switch to one of the newer versions. you can look at some of the recent commits on how to open a PR for doing this. (https://github.com/projectkudu/AzureResourceExplorer/#adding-swagger-specs)

For immediate mitigation, you can try using a different client.