You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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 Version
1.4.6
AzureRM Provider Version
3.58.0
Affected Resource(s)/Data Source(s)
all
Terraform Configuration Files
Use any terraform files. The error is already happening when the planning phase is initialized.
Debug Output/Panic Output
Planning failed. Terraform encountered an error while generating this plan.
╷
│ Error: Error ensuring Resource Providers are registered.
│
│ Terraform automatically attempts to register the Resource Providers it supports to
│ ensure it's able to provision resources.│ │ If you don't have permission to register Resource Providers you may wish to use the
│ "skip_provider_registration" flag in the Provider block to disable this functionality.
│
│ Please note that if you opt out of Resource Provider Registration and Terraform tries
│ to provision a resource from a Resource Provider which is unregistered, then the errors
│ may appear misleading - for example:
│
│ > API version 2019-XX-XX was not found for Microsoft.Foo
│
│ Could indicate either that the Resource Provider "Microsoft.Foo" requires registration,
│ but this could also indicate that this Azure Region doesn't support this API version.│ │ More information on the "skip_provider_registration" flag can be found here:│ https://registry.terraform.io/providers/hashicorp/azurerm/latest/docs#skip_provider_registration│ │ Original Error: determining which Required Resource Providers require registration: the required Resource Provider "Microsoft.Maps" wasn't returned from the Azure API
│
│ with provider["registry.terraform.io/hashicorp/azurerm"],
│ on provider.tf line 18, in provider "azurerm":
│ 18: provider "azurerm" {
│
╵
Expected Behaviour
When using ARM_ENVIRONMENT=china the error above should not happen on plan.
Actual Behaviour
The error above should happens on terraform plan when ARM_ENVIRONMENT=china is set.
Steps to Reproduce
Set ARM_ENVIRONMENT=china
Execute terraform plan
Important Factoids
Happens only when trying to deploy to Azure China
References
No response
The text was updated successfully, but these errors were encountered:
This is related to #21695 and appears to be a duplicate of #21785. I'm also experiencing this issue in an AzurePublicCloud environment, so I don't think it is related to just AzureChina.
@PSanetra Thanks for taking the time to submit this issue. It looks like this is a duplicate of #21785. We like to try to keep discussions consolidated, so we’re going to close this new issue in favor of #21785, please track issue #21785 for updates and 👍 the original issue to help us track community interest and experience.
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.
Is there an existing issue for this?
Community Note
Terraform Version
1.4.6
AzureRM Provider Version
3.58.0
Affected Resource(s)/Data Source(s)
all
Terraform Configuration Files
Debug Output/Panic Output
Expected Behaviour
When using
ARM_ENVIRONMENT=china
the error above should not happen on plan.Actual Behaviour
The error above should happens on
terraform plan
whenARM_ENVIRONMENT=china
is set.Steps to Reproduce
ARM_ENVIRONMENT=china
terraform plan
Important Factoids
Happens only when trying to deploy to Azure China
References
No response
The text was updated successfully, but these errors were encountered: