Skip to content
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

azurerm_autoscale_settings: tag "$type" is treated as changed on plan #1661

Closed
Supermathie opened this issue Jul 26, 2018 · 2 comments · Fixed by #1770
Closed

azurerm_autoscale_settings: tag "$type" is treated as changed on plan #1661

Supermathie opened this issue Jul 26, 2018 · 2 comments · Fixed by #1770

Comments

@Supermathie
Copy link
Contributor

Supermathie commented Jul 26, 2018

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 Version

Terraform v0.11.7

  • provider.azurerm v1.11.0
  • provider.random v1.3.1
  • provider.template v1.0.0

Affected Resource(s)

  • azurerm_autoscale_settings

Terraform Configuration Files

resource "azurerm_autoscale_setting" "app" {
  name                = "${var.label}DefaultSettings"
  resource_group_name = "${azurerm_resource_group.app.name}"
  location            = "${azurerm_resource_group.app.location}"
  target_resource_id  = "${azurerm_virtual_machine_scale_set.app.id}"

  tags {
    Cluster = "${var.label}"
    DC = "${terraform.workspace}"
  }
…
}

Debug Output

Panic Output

Expected Behavior

After a clean apply, a re-plan should show no changes

Actual Behavior

An execution plan has been generated and is shown below.
Resource actions are indicated with the following symbols:
  ~ update in-place

Terraform will perform the following actions:

  ~ module.coffee_cluster.azurerm_autoscale_setting.app
      tags.$type: "Microsoft.WindowsAzure.Management.Common.Storage.CasePreservedDictionary, Microsoft.WindowsAzure.Management.Common.Storage" => ""
      tags.%:     "3" => "2"

  ~ module.discuss_cluster.azurerm_autoscale_setting.app
      tags.$type: "Microsoft.WindowsAzure.Management.Common.Storage.CasePreservedDictionary, Microsoft.WindowsAzure.Management.Common.Storage" => ""
      tags.%:     "3" => "2"

  ~ module.meta_cluster.azurerm_autoscale_setting.app
      tags.$type: "Microsoft.WindowsAzure.Management.Common.Storage.CasePreservedDictionary, Microsoft.WindowsAzure.Management.Common.Storage" => ""
      tags.%:     "3" => "2"

  ~ module.sushi_cluster.azurerm_autoscale_setting.app
      tags.$type: "Microsoft.WindowsAzure.Management.Common.Storage.CasePreservedDictionary, Microsoft.WindowsAzure.Management.Common.Storage" => ""
      tags.%:     "3" => "2"


Plan: 0 to add, 4 to change, 0 to destroy.

Steps to Reproduce

  1. terraform apply
  2. terraform apply

Important Factoids

References

@tombuildsstuff
Copy link
Contributor

hi @Supermathie

Thanks for reporting this issue - just to let you know that a fix for this issue has been released as part of v1.13.0 of the AzureRM Provider :)

Thanks!

@ghost
Copy link

ghost commented Mar 30, 2020

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 feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. If you feel I made an error 🤖 🙉 , please reach out to my human friends 👉 [email protected]. Thanks!

@ghost ghost locked and limited conversation to collaborators Mar 30, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants