2.65.0 - SDK for Eventhub Namespaces 2021-01-01-preview not available in Azure China

[mhennecke]

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment

Terraform (and AzureRM Provider) Version

Terraform v0.14.9
+ provider registry.terraform.io/hashicorp/azurerm v2.65.0

Affected Resource(s)

• azurerm_eventhub_namespace

Expected Behaviour

Plan and apply of Event Hub Namespace resources in Azure China should work.

Actual Behaviour

Refresh during plan fails with the following:

Error: retrieving Namespace: (Name "xxx" / Resource Group "xxx"): namespaces.NamespacesClient#Get: Failure responding to request: StatusCode=400 -- Original Error: autorest/azure: Service returned an error.
Status=400
Code="NoRegisteredProviderFound"
Message="No registered resource provider found for location 'chinaeast2' and API version '2021-01-01-preview' for type 'namespaces'. The supported api-versions are '2014-09-01, 2015-08-01, 2017-04-01, 2018-01-01-preview'. The supported locations are 'chinanorth, chinaeast, chinanorth2, chinaeast2'."

Steps to Reproduce

1. Prerequisite: State with at least one Event Hub namespace created with a provider version <2.65.0 in Azure China
2. Update azurerm provider version to 2.65.0
3. terraform plan

Important Factoids

Only observed in Azure China. Maybe also relevant for other sovereign clouds.

References

• eventhub: updating the namespace SDK to use API Version 2021-01-01-preview #12290

[mhennecke]

Issue seems to be resolved in Azure China. At least according to our lastest run with provider version 2.68.0 on the 18th of July 2021

[github-actions]

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.