Ask Questions Elsewhere
hi @XXX
Thanks for opening this issue.
This forum is intended to be used for feature enhancements and bugs in the Azure Provider - so that we can keep this forum focused on that we instead ask that broader questions are raised [using one of the Community Resources](https://www.terraform.io/docs/extend/community/index.html). As such I'm going to close this issue for the moment, but I believe you should be able to get an answer for this [using one of the Community Resources](https://www.terraform.io/docs/extend/community/index.html) (such as Stack Overflow).
Thanks!
Core - dependency on name
hey @XXX
Thanks for opening this issue.
Taking a look into this unfortunately this appears to be a bug in Terraform Core and as such would need to be fixed there. There's an upstream issue tracking this (https://github.com/hashicorp/terraform/issues/8099) where the Terraform Core team should be able to take a look and make a fix; but once the fix is added that should automatically become available to all providers. Since this isn't something we're able to work around in the Azure Provider directly; for the moment I'm going to close this in favour of the upstream issue https://github.com/hashicorp/terraform/issues/8099 - would you mind subscribing to that issue for updates?
Thanks!
Duplicate
hi @XXX
Thanks for opening this issue :)
Taking a look through this appears to be a duplicate of #XXX - rather than having multiple issues open tracking the same thing I'm going to close this issue in favour of that one; would you mind subscribing to #XXX for updates?
Thanks!
Feature Already Available
hi @XXX
Thanks for opening this issue :)
As @XXX has mentioned (thanks!) I believe this functionality is available via the `XXX` field within the `XXX` resource - would you be able to take a look and see if that works for you?Since this functionality appears to be supported I'm going to close this issue for the moment - however please let us know if that doesn't work for you and we'll take another look.
Thanks!
Fixed in release
hi @
Just to let you know that support for this shipped in v1.XXX - you can upgrade to this by updating the version in the Provider block (as shown below) and then running `terraform init -upgrade`:
[][][]
provider "azurerm" {
version = "=1.XXX.0"
}
[][][]
Thanks!
Please Upgrade
hi @XXX
Thanks for opening this issue.
Taking a look into this this has been fixed in a newer version of the Azure Provider - we're currently on version XXX - which you can upgrade to by updating the version in the Provider block (as shown below) and then running `terraform init -upgrade`:
[][][]
provider "azurerm" {
version = "=1.XX.X"
}
[][][]
.. which should solve this for you - would you be able to take a look and see if that works for you?
Thanks!
Temporarily Closing whilst the API's broken
👋
Since this PR is blocked on the upstream issue, rather than leaving this PR open blocked until that's resolved I'm going to temporarily close this PR for the moment (and assign this to the `Blocked` milestone). Once [the upstream issue](XXX) has been resolved we'll circle back to this and take another look/get this merged 👍
Thanks!
Terraform registers resource providers
hi @XXXX
Thanks for opening this issue :)
Azure's concept of a Resource Provider requires that the Resource Provider is registered before any API's within that Resource Provider can be called. As such, rather than failing during an API call / to improve the user experience Terraform automatically attempts to register any Resource Providers that it supports by default - to ensure that the API's are available when they're needed; and since this list is stored within Terraform, we extend this list from time to time as Terraform is updated to support new functionality (provided in new Resource Providers).
If you'd prefer to manage Resource Provider Registration outside of Terraform (for example you're running in a restricted environment) - it's possible to opt-out of this behaviour by setting this field [in the Provider block](https://www.terraform.io/docs/providers/azurerm/index.html#skip_provider_registration).
Since this is working as intended I'm going to close this issue for the moment - but please let us know if disabling this functionality doesn't work for you and we'll take another look.
Thanks!
Upstream Broken Issue
hi @XXX
Thanks for opening this issue.
Just to let you know that unfortunately this is blocked on [an upstream bug in the Azure API's which is being tracked here](XXX) - once that's resolved it'll be possible for someone to take a look into this. Until that's resolved there's not a lot we can do with this unfortunately, as such for the moment I'm going to tag this as `upstream-microsoft` (which we use to indicate this issue is blocked upstream).
Thanks!