Skip to content

Commit a23c7a5

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

File tree

2 files changed

+48
-6
lines changed

2 files changed

+48
-6
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/datadogV2/api/api_security_monitoring.rs

Lines changed: 24 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1744,7 +1744,12 @@ impl SecurityMonitoringAPI {
17441744
}
17451745

17461746
/// Convert an existing rule from JSON to Terraform for datadog provider
1747-
/// resource datadog_security_monitoring_rule.
1747+
/// resource `datadog_security_monitoring_rule`. You can do so for the following rule types:
1748+
/// - App and API Protection
1749+
/// - Cloud SIEM (log detection and signal correlation)
1750+
/// - Workload Protection
1751+
///
1752+
/// 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>).
17481753
pub async fn convert_existing_security_monitoring_rule(
17491754
&self,
17501755
rule_id: String,
@@ -1770,7 +1775,12 @@ impl SecurityMonitoringAPI {
17701775
}
17711776

17721777
/// Convert an existing rule from JSON to Terraform for datadog provider
1773-
/// resource datadog_security_monitoring_rule.
1778+
/// resource `datadog_security_monitoring_rule`. You can do so for the following rule types:
1779+
/// - App and API Protection
1780+
/// - Cloud SIEM (log detection and signal correlation)
1781+
/// - Workload Protection
1782+
///
1783+
/// 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>).
17741784
pub async fn convert_existing_security_monitoring_rule_with_http_info(
17751785
&self,
17761786
rule_id: String,
@@ -2000,7 +2010,12 @@ impl SecurityMonitoringAPI {
20002010
}
20012011

20022012
/// Convert a rule that doesn't (yet) exist from JSON to Terraform for datadog provider
2003-
/// resource datadog_security_monitoring_rule.
2013+
/// resource `datadog_security_monitoring_rule`. You can do so for the following rule types:
2014+
/// - App and API Protection
2015+
/// - Cloud SIEM (log detection and signal correlation)
2016+
/// - Workload Protection
2017+
///
2018+
/// 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>).
20042019
pub async fn convert_security_monitoring_rule_from_json_to_terraform(
20052020
&self,
20062021
body: crate::datadogV2::model::SecurityMonitoringRuleConvertPayload,
@@ -2026,7 +2041,12 @@ impl SecurityMonitoringAPI {
20262041
}
20272042

20282043
/// Convert a rule that doesn't (yet) exist from JSON to Terraform for datadog provider
2029-
/// resource datadog_security_monitoring_rule.
2044+
/// resource `datadog_security_monitoring_rule`. You can do so for the following rule types:
2045+
/// - App and API Protection
2046+
/// - Cloud SIEM (log detection and signal correlation)
2047+
/// - Workload Protection
2048+
///
2049+
/// 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>).
20302050
pub async fn convert_security_monitoring_rule_from_json_to_terraform_with_http_info(
20312051
&self,
20322052
body: crate::datadogV2::model::SecurityMonitoringRuleConvertPayload,

0 commit comments

Comments
 (0)