Fail to apply AppInsight using a workspace in AureRM 3.33

[Pumkko]

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

Terraform Version

1.3.5

AzureRM Provider Version

3.33

Affected Resource(s)/Data Source(s)

azurerm_application_insights

Terraform Configuration Files

resource "azurerm_application_insights" "kimAppInsight" {
  name                = "kim-${terraform.workspace}-ai"
  location            = var.SERVICE_PLAN_LOCATION
  resource_group_name = azurerm_resource_group.kimResourceGroup.name
  workspace_id        = var.ANALYTIC_WORKSPACE_ID
  application_type    = "web"
}

Debug Output/Panic Output

parsing "/subscriptions/[SubscriptionId]/resourcegroups/monitoring-dev-rg/providers/microsoft.operationalinsights/workspaces/monitoring-dev-log": parsing segment "staticResourceGroups": expected the segment "resourcegroups" to be "resourceGroups"

with azurerm_application_insights.kimAppInsight,
 on appinsights.tf line 6, in resource "azurerm_application_insights" "kimAppInsight":
  workspace_id        = var.ANALYTIC_WORKSPACE_ID

Expected Behaviour

The command terraform apply works well when using azurrm provider v3.32, the id given to workspace is correct i double checked it using azure CLI.

Actual Behaviour

No response

Steps to Reproduce

No response

Important Factoids

No response

References

No response

[ms-zhenhua]

Hi @Pumkko, seems there is a change in v3.33 and you could try to replace resourcegroups in var.ANALYTIC_WORKSPACE_ID with resourceGroups to resolve this issue.

[Pumkko]

Hi @Pumkko, seems there is a change in v3.33 and you could try to replace resourcegroups in var.ANALYTIC_WORKSPACE_ID with resourceGroups to resolve this issue.

Thanks for your reply, i did try that but the problem persisted, right now we avoid the issue by using version 3.32

[github-actions]

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 have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.