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
AzureRM Version 2.42.0 casing issues with respect to Log Analytics Workspace Id leads to replacement of Azurerm Monitor Diagnostic Setting resource
#10165
This has been fixed in #10104 and will become available in version v2.43.0 of the Azure Provider - since support for this has been merged I'm going to close this issue for the moment; however I've assigned this to the v2.43.0 milestone so @hashibot will comment when the release is available.
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
locked as resolved and limited conversation to collaborators
Feb 12, 2021
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Community Note
Terraform (and AzureRM Provider) Version
Terraform Version: 0.13.0
AzureRM Provider Version: 2.42.0
Affected Resource(s)
azurerm_monitor_diagnostic_setting
Terraform Configuration Files
Debug Output
Panic Output
Expected Behaviour
The
log_analytics_workspace_id
casing of Microsoft.OperationalInsights and resourceGroups should not lead to a replacement of the diagnostic setting.Actual Behaviour
Steps to Reproduce
terraform plan
(optionally: 2.
terraform apply
)Important Factoids
Location is WestEurope, but probably does not matter.
References
None
The text was updated successfully, but these errors were encountered: