Skip to content

Commit 020621c

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

File tree

2 files changed

+36
-4
lines changed

2 files changed

+36
-4
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'

lib/datadog_api_client/v2/api/security_monitoring_api.rb

Lines changed: 12 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -105,7 +105,12 @@ def convert_existing_security_monitoring_rule(rule_id, opts = {})
105105
# Convert an existing rule from JSON to Terraform.
106106
#
107107
# Convert an existing rule from JSON to Terraform for datadog provider
108-
# resource datadog_security_monitoring_rule.
108+
# resource `datadog_security_monitoring_rule`. You can do so for the following rule types:
109+
# - App and API Protection
110+
# - Cloud SIEM (log detection and signal correlation)
111+
# - Workload Protection
112+
#
113+
# You can convert Cloud Security configuration rules using Terraform's [Datadog Cloud Configuration Rule resource](https://registry.terraform.io/providers/DataDog/datadog/latest/docs/resources/cloud_configuration_rule).
109114
#
110115
# @param rule_id [String] The ID of the rule.
111116
# @param opts [Hash] the optional parameters
@@ -244,7 +249,12 @@ def convert_security_monitoring_rule_from_json_to_terraform(body, opts = {})
244249
# Convert a rule from JSON to Terraform.
245250
#
246251
# Convert a rule that doesn't (yet) exist from JSON to Terraform for datadog provider
247-
# resource datadog_security_monitoring_rule.
252+
# resource `datadog_security_monitoring_rule`. You can do so for the following rule types:
253+
# - App and API Protection
254+
# - Cloud SIEM (log detection and signal correlation)
255+
# - Workload Protection
256+
#
257+
# You can convert Cloud Security configuration rules using Terraform's [Datadog Cloud Configuration Rule resource](https://registry.terraform.io/providers/DataDog/datadog/latest/docs/resources/cloud_configuration_rule).
248258
#
249259
# @param body [SecurityMonitoringRuleConvertPayload]
250260
# @param opts [Hash] the optional parameters

0 commit comments

Comments
 (0)