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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

azurerm_app_service_managed_certificate does not save tags to Azure #25942

Open
1 task done
jakub-kuchta-nv opened this issue May 13, 2024 · 0 comments
Open
1 task done

Comments

@jakub-kuchta-nv
Copy link

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.8.2

AzureRM Provider Version

3.103.1

Affected Resource(s)/Data Source(s)

azurerm_app_service_managed_certificate

Terraform Configuration Files

resource "azurerm_app_service_managed_certificate" "cert" {
  {...}
  tags     = merge(local.tags, var.tags)
}

# we are using the above alongside azurerm_linux_web_app and azurerm_windows_web_app

Debug Output/Panic Output

resource "azurerm_app_service_managed_certificate" "cert" {
  id = "..."
  ~ tags                       = {
      + "..." = "..."
    }
    # (8 unchanged attributes hidden)
}

Expected Behaviour

Tags should be saved to the managed certificate

Actual Behaviour

Certificate resource tags are not saved on Azure.
Re-running terraform apply causes an update-in-place, with tags being modified on each run, but not persisted.

Steps to Reproduce

terraform apply

Important Factoids

No response

References

#11816 - there was a request to create a new issue if this still happens on version 3.x of the azurerm provider, as is the case

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants