Skip to content

Commit e3671ff

Browse files
author
ci.datadog-api-spec
committed
Regenerate client from commit 199abc9 of spec repo
1 parent e52f93c commit e3671ff

File tree

2 files changed

+38
-5
lines changed

2 files changed

+38
-5
lines changed

.generator/schemas/v2/openapi.yaml

Lines changed: 24 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -77969,7 +77969,18 @@ paths:
7796977969
description: 'Convert a rule that doesn''t (yet) exist from JSON to Terraform
7797077970
for datadog provider
7797177971

77972-
resource datadog_security_monitoring_rule.'
77972+
resource `datadog_security_monitoring_rule`. You can do so for the following
77973+
rule types:
77974+
77975+
- App and API Protection
77976+
77977+
- Cloud SIEM (log detection and signal correlation)
77978+
77979+
- Workload Protection
77980+
77981+
77982+
You can convert Cloud Security configuration rules using Terraform''s [Datadog
77983+
Cloud Configuration Rule resource](https://registry.terraform.io/providers/DataDog/datadog/latest/docs/resources/cloud_configuration_rule).'
7797377984
operationId: ConvertSecurityMonitoringRuleFromJSONToTerraform
7797477985
requestBody:
7797577986
content:
@@ -78188,7 +78199,18 @@ paths:
7818878199
get:
7818978200
description: 'Convert an existing rule from JSON to Terraform for datadog provider
7819078201

78191-
resource datadog_security_monitoring_rule.'
78202+
resource `datadog_security_monitoring_rule`. You can do so for the following
78203+
rule types:
78204+
78205+
- App and API Protection
78206+
78207+
- Cloud SIEM (log detection and signal correlation)
78208+
78209+
- Workload Protection
78210+
78211+
78212+
You can convert Cloud Security configuration rules using Terraform''s [Datadog
78213+
Cloud Configuration Rule resource](https://registry.terraform.io/providers/DataDog/datadog/latest/docs/resources/cloud_configuration_rule).'
7819278214
operationId: ConvertExistingSecurityMonitoringRule
7819378215
parameters:
7819478216
- $ref: '#/components/parameters/SecurityMonitoringRuleID'

src/main/java/com/datadog/api/client/v2/api/SecurityMonitoringApi.java

Lines changed: 14 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -301,8 +301,13 @@ public SecurityMonitoringRuleConvertResponse convertExistingSecurityMonitoringRu
301301
}
302302

303303
/**
304-
* Convert an existing rule from JSON to Terraform for datadog provider resource
305-
* datadog_security_monitoring_rule.
304+
* Convert an existing rule from JSON to Terraform for datadog provider resource <code>
305+
* datadog_security_monitoring_rule</code>. You can do so for the following rule types: - App and
306+
* API Protection - Cloud SIEM (log detection and signal correlation) - Workload Protection
307+
*
308+
* <p>You can convert Cloud Security configuration rules using Terraform's <a
309+
* href="https://registry.terraform.io/providers/DataDog/datadog/latest/docs/resources/cloud_configuration_rule">Datadog
310+
* Cloud Configuration Rule resource</a>.
306311
*
307312
* @param ruleId The ID of the rule. (required)
308313
* @return ApiResponse&lt;SecurityMonitoringRuleConvertResponse&gt;
@@ -598,7 +603,13 @@ public SecurityMonitoringRuleConvertResponse convertSecurityMonitoringRuleFromJS
598603

599604
/**
600605
* Convert a rule that doesn't (yet) exist from JSON to Terraform for datadog provider resource
601-
* datadog_security_monitoring_rule.
606+
* <code>datadog_security_monitoring_rule</code>. You can do so for the following rule types: -
607+
* App and API Protection - Cloud SIEM (log detection and signal correlation) - Workload
608+
* Protection
609+
*
610+
* <p>You can convert Cloud Security configuration rules using Terraform's <a
611+
* href="https://registry.terraform.io/providers/DataDog/datadog/latest/docs/resources/cloud_configuration_rule">Datadog
612+
* Cloud Configuration Rule resource</a>.
602613
*
603614
* @param body (required)
604615
* @return ApiResponse&lt;SecurityMonitoringRuleConvertResponse&gt;

0 commit comments

Comments
 (0)