Skip to content

Add rule type conversion limitations for Security Monitoring #3005

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: v2
Choose a base branch
from
Open

Add rule type conversion limitations for Security Monitoring #3005

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
26 changes: 24 additions & 2 deletions .generator/schemas/v2/openapi.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -77969,7 +77969,18 @@ paths:
description: 'Convert a rule that doesn''t (yet) exist from JSON to Terraform
for datadog provider

resource datadog_security_monitoring_rule.'
resource `datadog_security_monitoring_rule`. You can do so for the following
rule types:

- App and API Protection

- Cloud SIEM (log detection and signal correlation)

- Workload Protection


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).'
operationId: ConvertSecurityMonitoringRuleFromJSONToTerraform
requestBody:
content:
Expand Down Expand Up @@ -78188,7 +78199,18 @@ paths:
get:
description: 'Convert an existing rule from JSON to Terraform for datadog provider

resource datadog_security_monitoring_rule.'
resource `datadog_security_monitoring_rule`. You can do so for the following
rule types:

- App and API Protection

- Cloud SIEM (log detection and signal correlation)

- Workload Protection


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).'
operationId: ConvertExistingSecurityMonitoringRule
parameters:
- $ref: '#/components/parameters/SecurityMonitoringRuleID'
Expand Down
14 changes: 12 additions & 2 deletions services/security_monitoring/src/v2/SecurityMonitoringApi.ts
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -9688,7 +9688,12 @@ export class SecurityMonitoringApi {

/**
* Convert an existing rule from JSON to Terraform for datadog provider
* resource datadog_security_monitoring_rule.
* resource `datadog_security_monitoring_rule`. You can do so for the following rule types:
* - App and API Protection
* - Cloud SIEM (log detection and signal correlation)
* - Workload Protection
*
* 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).
* @param param The request object
*/
public convertExistingSecurityMonitoringRule(
Expand Down Expand Up @@ -9736,7 +9741,12 @@ export class SecurityMonitoringApi {

/**
* Convert a rule that doesn't (yet) exist from JSON to Terraform for datadog provider
* resource datadog_security_monitoring_rule.
* resource `datadog_security_monitoring_rule`. You can do so for the following rule types:
* - App and API Protection
* - Cloud SIEM (log detection and signal correlation)
* - Workload Protection
*
* 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).
* @param param The request object
*/
public convertSecurityMonitoringRuleFromJSONToTerraform(
Expand Down