datadog_security_monitoring_rules (Data Source) errors on "Log4Shell Scanning Detected" default rule

[agfunderburg10]

Hi there,

Thank you for opening an issue. Please note that we try to keep the Terraform issue tracker reserved for bug reports and feature requests. For general usage questions, please see: https://www.terraform.io/community.html.

Terraform Version

Terraform v1.1.9 on linux_arm64

Affected Resource(s)

• datadog_security_monitoring_rules

Terraform Configuration Files

This is used in the component:

data "datadog_security_monitoring_rules" "default_rules" {
  default_only_filter = true
}

Debug Output

https://gist.github.com/agfunderburg10/8e63adbbad74d5d0e2236027e19b1039

Expected Behavior

The data source should successfully obtain the data from the DataDog default Security Detection rules.

Actual Behavior

It fails to do so because something with this specific rule is not supported.

Steps to Reproduce

Please list the steps required to reproduce the issue, for example:

1. Verify you have the "Log4Shell Scanning Detected" default rule in the Security Detection Rules. (Since this is a default, I assume it was created by DataDog)
2. Deploy a terraform component that attempts to pull the rule data

data "datadog_security_monitoring_rules" "default_rules" {
  default_only_filter = true
}

3. terraform apply
4. You should receive the error

Important Factoids

I have tried this with versions 3.6, 3.9, 3.10, and 3.11 of the datadog provider. All are broken (some give difference errors though)

[skarimo]

Thanks for the report. This was resolved by: DataDog/datadog-api-client-go#1493 and should be in the next release