azurerm_monitor_activity_log_alert - support for levels, resource_providers, resource_types, resource_groups, resource_ids, statuses,and sub_statuses properties

[teowa]

resolves #21186
resolves #20759
resolves #21496

TF_ACC=1 go test -v ./internal/services/monitor -parallel 20 -test.run=TestAccMonitorActivityLogAlert_listCriteria -timeout 1440m -ldflags="-X=github.com/hashicorp/terraform-provider-azurerm/version.ProviderVersion=acc"
=== RUN   TestAccMonitorActivityLogAlert_listCriteria
=== PAUSE TestAccMonitorActivityLogAlert_listCriteria
=== CONT  TestAccMonitorActivityLogAlert_listCriteria
--- PASS: TestAccMonitorActivityLogAlert_listCriteria (204.76s)
PASS
ok      github.com/hashicorp/terraform-provider-azurerm/internal/services/monitor       204.786s

[katbyte]

are there not constants for these in the SDK? if not could we open an issue on the rest specs to have them added?

[teowa]

The API only specifies the condition should be key-value pairs, and there is no enum for values.

And more details on property mappings:
level corresponds to:

{
      "field": "level",
      "equals": "Verbose"
},

levels corresponds to:

{
    "anyOf": [
        {
            "field": "level",
            "equals": "Verbose"
        },
        {
            "field": "level",
            "equals": "Informational"
        }
    ]
},

or

{
      "field": "level",
      "containsAny": ["Verbose", "Informational"]
},

since levels may map to 2 REST API schemas, here I am using the anyOf one in create/update, but accept either one in read.

[katbyte]

LGTM 🦀

[github-actions]

This functionality has been released in v3.58.0 of the Terraform Provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading.

For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template. Thank you!

[github-actions]

I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active contributions.
If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.