-
Notifications
You must be signed in to change notification settings - Fork 4.6k
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
Case sensitivity issue with azurerm_kubernetes_cluster #17090
Comments
This was initially built through the azure portal and then imported into terraform. |
For us, it appears the resource ID generated by the resource "azurerm_kubernetes_cluster" "freight_science_kube" {
...
oms_agent {
log_analytics_workspace_id = azurerm_log_analytics_workspace.log_analytics_workspace.id
}
...
}
resource "azurerm_log_analytics_workspace" "log_analytics_workspace" {
name = "workspace-name"
...
}
|
After talking with @tombuildsstuff, he stated this is a formatter issue and will be resolved down the road when the log analytics resource is updated. However, a workaround is to |
Thanks for raising this issue @jwshive. I believe this should have been resolved by #20484 which case insensitively parses the resource ID for the log analytics workspace. Upgrading to v3.44.0+ should fix this for you. I'm going to go ahead and close this for now. If you're still facing issues with the segment casing of the resource ID please let us know and we can reopen this! |
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. |
Is there an existing issue for this?
Community Note
Terraform Version
1.2.2
AzureRM Provider Version
3.8.0
Affected Resource(s)/Data Source(s)
azurerm_kubernetes_cluster
Terraform Configuration Files
Debug Output/Panic Output
Expected Behaviour
Resource isn't replaced
Actual Behaviour
Because of the case issues with "resourceGroup" vs "resourcegroup" the resource is constantly replaced. A lifecycle block mitigates this but should now be required.
Steps to Reproduce
No response
Important Factoids
No response
References
No response
The text was updated successfully, but these errors were encountered: