@@ -79133,9 +79133,20 @@ paths:
7913379133 /api/v2/security_monitoring/rules/convert:
7913479134 post:
7913579135 description: 'Convert a rule that doesn''t (yet) exist from JSON to Terraform
79136- for datadog provider
79136+ for Datadog provider
7913779137
79138- resource datadog_security_monitoring_rule.'
79138+ resource `datadog_security_monitoring_rule`. You can do so for the following
79139+ rule types:
79140+
79141+ - App and API Protection
79142+
79143+ - Cloud SIEM (log detection and signal correlation)
79144+
79145+ - Workload Protection
79146+
79147+
79148+ You can convert Cloud Security configuration rules using Terraform''s [Datadog
79149+ Cloud Configuration Rule resource](https://registry.terraform.io/providers/DataDog/datadog/latest/docs/resources/cloud_configuration_rule).'
7913979150 operationId: ConvertSecurityMonitoringRuleFromJSONToTerraform
7914079151 requestBody:
7914179152 content:
@@ -79352,9 +79363,20 @@ paths:
7935279363 - security_monitoring_rules_write
7935379364 /api/v2/security_monitoring/rules/{rule_id}/convert:
7935479365 get:
79355- description: 'Convert an existing rule from JSON to Terraform for datadog provider
79366+ description: 'Convert an existing rule from JSON to Terraform for Datadog provider
79367+
79368+ resource `datadog_security_monitoring_rule`. You can do so for the following
79369+ rule types:
79370+
79371+ - App and API Protection
79372+
79373+ - Cloud SIEM (log detection and signal correlation)
79374+
79375+ - Workload Protection
79376+
7935679377
79357- resource datadog_security_monitoring_rule.'
79378+ You can convert Cloud Security configuration rules using Terraform''s [Datadog
79379+ Cloud Configuration Rule resource](https://registry.terraform.io/providers/DataDog/datadog/latest/docs/resources/cloud_configuration_rule).'
7935879380 operationId: ConvertExistingSecurityMonitoringRule
7935979381 parameters:
7936079382 - $ref: '#/components/parameters/SecurityMonitoringRuleID'
0 commit comments