azurerm_monitor_diagnostic_setting error out when only log is specified with 3.71.0

[juicybaba]

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 and review the contribution guide to help.

Terraform Version

1.5.4

AzureRM Provider Version

3.71.0

Affected Resource(s)/Data Source(s)

azurerm_monitor_diagnostic_setting

Terraform Configuration Files

resource "azurerm_monitor_diagnostic_setting" "databricks_diag_setting" {
  name                       = "***"
  target_resource_id         = "***"
  log_analytics_workspace_id = "***"

  log {
    category = "***"
    enabled  = true

    retention_policy {
      days    = 90
      enabled = true
    }
  }
}

Debug Output/Panic Output

Error: Missing required argument
with azurerm_monitor_diagnostic_setting.databricks_diag_setting
on resources.diagsettings.tf line 96, in resource "azurerm_monitor_diagnostic_setting" "databricks_diag_setting":
resource "azurerm_monitor_diagnostic_setting" "databricks_diag_setting" {
"enabled_log": one of `enabled_log,metric` must be specified

Expected Behaviour

The code should work. And the code worked with 3.70.0. It looks like an azurerm 4.0 breaking change is partially released with this PR.

https://github.com/hashicorp/terraform-provider-azurerm/pull/23024/files#diff-a63d5b7afa0481d351b89b738291b612e9bbf364bc1edf6ce8c2ed3d66c735bb

Actual Behaviour

No response

Steps to Reproduce

No response

Important Factoids

No response

References

No response

[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.