-
Notifications
You must be signed in to change notification settings - Fork 4.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Tags on EventHubNamespace do not work properly #12003
Comments
Hi, I can confirm the whole point. it detect now drift with all tags since we updated last version 2.61 Thanks |
The problem isn't present in version 2.60. |
i thought maybe this was our blueprint doing something bad..but guess it's terraform. No plan comes back as clean now :( |
I'm having the same issue. I tried with terraform 0.14.0 and 0.14.11, azurerm provider 2.22.0 and 2.62.0. I tried a couple of combination without success. Looks like it takes one of the tags value randomly, and applies its value to all other tags. |
Fixed via #12062 |
This has been released in version 2.63.0 of the provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. As an example: provider "azurerm" {
version = "~> 2.63.0"
}
# ... other configuration ... |
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. |
Hi there,
azurerm doesn't fetch the tags from an eventhub_namespace as expected.
Please see below for details.
Community Note
Terraform (and AzureRM Provider) Version
Verifying Terraform installation...
/opt/hostedtoolcache/terraform/0.15.4/x64/terraform version
Terraform v0.15.4
on linux_amd64
Initializing provider plugins...
Affected Resource(s)
Terraform Configuration Files
Expected Behaviour
"terraform apply" applies the tags correctly
after applying the next "terraform plan" should show no changes
Actual Behaviour
"terraform apply" applies the tags correctly
after applying the next "terraform plan shows:
Somehow the tags are incorrectly read by azurerm from the eventhub_namespace.
The tags are correctly displayed in Azure Portal.
The text was updated successfully, but these errors were encountered: