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_key_vault_managed_hardware_security_module tags forces replacement #24309

Closed
1 task done
williamarobinson opened this issue Dec 21, 2023 · 1 comment · Fixed by #24333
Closed
1 task done
Milestone

Comments

@williamarobinson
Copy link

williamarobinson commented Dec 21, 2023

Is there an existing issue for this?

  • I have searched the existing issues

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 and review the contribution guide to help.

Terraform Version

1.6.6

AzureRM Provider Version

3.85.0

Affected Resource(s)/Data Source(s)

azurerm_key_vault_managed_hardware_security_module

Terraform Configuration Files

resource "azurerm_key_vault" "example" {
  name                        = "example-key-vault"
  resource_group_name         = azurerm_resource_group.example.name
  location                    = azurerm_resource_group.example.location
  enabled_for_disk_encryption = true
  tenant_id                   = "<your-tenant-id>"
  sku_name                    = "Standard_B1"

  tags = {
    environment = "Dev"
    owner       = "terraform-team"
  }
}

Debug Output/Panic Output

- tags                                      = {
          - "Environment" = "Dev"
        } -> null # forces replacement

----
Plan: 1 to add, 0 to change, 1 to destroy.

Expected Behaviour

No replacement required

Actual Behaviour

Forces Replacement

Steps to Reproduce

No response

Important Factoids

No response

References

No response

Copy link

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.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Apr 28, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
1 participant