You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
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
The text was updated successfully, but these errors were encountered:
Is there an existing issue for this?
Community Note
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
Debug Output/Panic Output
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
The text was updated successfully, but these errors were encountered: