-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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_security_center_workspace": parsing segment "staticResourceGroups": expected the segment "resourcegroups" to be "resourceGroups #18360
Comments
Hi @darren-johnson thanks for opening the issue! The issue seems to be similar to #17426, I'll be checking if we could apply the same fix for this. |
Hi @myc2h6o, This is identical to #18244 which was incorrectly closed as a duplicate. I've added some information to the bottom of that ticket here #18244 (comment) The issue is a result of a lower cased resource ID being stored in Azure from a previous version of the provider. After upgrade to 3.21.0 or above, the provider is incorrectly doing a case sensitive parse of the returned value from the Azure API. Happy to send on some diagnostics information if you'd like |
Hey @myc2h6o and @tombuildsstuff , As per 18244, the response string from Azure is not the correct case. I've also looked at older LAW's and their id is There could be an issue in the I can put together a PR if that's helpful? |
`azurerm_monitor_diagnostic_settings`: fix casing parsing `azurerm_user_assigned_identity`: fix casing parsing `azurerm_security_center_workspace`: fix casing parsing Fixes hashicorp#18346 Fixes hashicorp#14853 Fixes hashicorp#18360
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.9
AzureRM Provider Version
3.22.0
Affected Resource(s)/Data Source(s)
azurerm_security_center_workspace
Terraform Configuration Files
Debug Output/Panic Output
Expected Behaviour
Should work.
Appears the same issue as #18235 .
Actual Behaviour
Brand new configuration which fails to deploy or destroy. Other security center resources are present in state and need removing via the CLI to destroy.
Error: Reading Security Center Log Analytics Workspace ID: parsing "/subscriptions/SUB_ID/resourcegroups/RG_NAME/providers/microsoft.operationalinsights/workspaces/WORKSPACE_NAME": parsing segment "staticResourceGroups": expected the segment "resourcegroups" to be "resourceGroups"
Present in state file as per below:
Steps to Reproduce
No response
Important Factoids
No response
References
No response
The text was updated successfully, but these errors were encountered: