Skip to content

Commit 0034201

Browse files
api-clients-generation-pipeline[bot]ci.datadog-api-spec
andauthored
GA Security Monitoring Rule Converter (#2048)
* Regenerate client from commit be099b30 of spec repo * pre-commit fixes --------- Co-authored-by: ci.datadog-api-spec <[email protected]> Co-authored-by: api-clients-generation-pipeline[bot] <54105614+api-clients-generation-pipeline[bot]@users.noreply.github.com>
1 parent 2def85c commit 0034201

File tree

6 files changed

+6
-16
lines changed

6 files changed

+6
-16
lines changed

.apigentools-info

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -4,13 +4,13 @@
44
"spec_versions": {
55
"v1": {
66
"apigentools_version": "1.6.6",
7-
"regenerated": "2024-07-19 17:23:31.128268",
8-
"spec_repo_commit": "e7026d11"
7+
"regenerated": "2024-07-19 18:52:07.831612",
8+
"spec_repo_commit": "be099b30"
99
},
1010
"v2": {
1111
"apigentools_version": "1.6.6",
12-
"regenerated": "2024-07-19 17:23:31.145349",
13-
"spec_repo_commit": "e7026d11"
12+
"regenerated": "2024-07-19 18:52:07.850438",
13+
"spec_repo_commit": "be099b30"
1414
}
1515
}
1616
}

.generator/schemas/v2/openapi.yaml

Lines changed: 0 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -33741,8 +33741,6 @@ paths:
3374133741
tags:
3374233742
- Security Monitoring
3374333743
x-codegen-request-body-name: body
33744-
x-unstable: '**Note**: This feature is in private beta. Reach out to support
33745-
to request access.'
3374633744
/api/v2/security_monitoring/rules/test:
3374733745
post:
3374833746
description: Test a rule.
@@ -33931,8 +33929,6 @@ paths:
3393133929
summary: Convert an existing rule from JSON to Terraform
3393233930
tags:
3393333931
- Security Monitoring
33934-
x-unstable: '**Note**: This feature is in private beta. Reach out to support
33935-
to request access.'
3393633932
/api/v2/security_monitoring/rules/{rule_id}/test:
3393733933
post:
3393833934
description: Test an existing rule.

examples/v2/security-monitoring/ConvertExistingSecurityMonitoringRule.py

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,6 @@
1010
SECURITY_RULE_ID = environ["SECURITY_RULE_ID"]
1111

1212
configuration = Configuration()
13-
configuration.unstable_operations["convert_existing_security_monitoring_rule"] = True
1413
with ApiClient(configuration) as api_client:
1514
api_instance = SecurityMonitoringApi(api_client)
1615
response = api_instance.convert_existing_security_monitoring_rule(

examples/v2/security-monitoring/ConvertSecurityMonitoringRuleFromJSONToTerraform.py

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -53,7 +53,6 @@
5353
)
5454

5555
configuration = Configuration()
56-
configuration.unstable_operations["convert_security_monitoring_rule_from_json_to_terraform"] = True
5756
with ApiClient(configuration) as api_client:
5857
api_instance = SecurityMonitoringApi(api_client)
5958
response = api_instance.convert_security_monitoring_rule_from_json_to_terraform(body=body)

src/datadog_api_client/configuration.py

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -265,8 +265,6 @@ def __init__(
265265
"v2.update_incident_todo": False,
266266
"v2.query_scalar_data": False,
267267
"v2.query_timeseries_data": False,
268-
"v2.convert_existing_security_monitoring_rule": False,
269-
"v2.convert_security_monitoring_rule_from_json_to_terraform": False,
270268
"v2.get_finding": False,
271269
"v2.list_findings": False,
272270
"v2.mute_findings": False,

tests/v2/features/security_monitoring.feature

Lines changed: 2 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -73,8 +73,7 @@ Feature: Security Monitoring
7373

7474
@team:DataDog/k9-cloud-security-platform
7575
Scenario: Convert a rule from JSON to Terraform returns "OK" response
76-
Given operation "ConvertSecurityMonitoringRuleFromJSONToTerraform" enabled
77-
And new "ConvertSecurityMonitoringRuleFromJSONToTerraform" request
76+
Given new "ConvertSecurityMonitoringRuleFromJSONToTerraform" request
7877
And body with value {"name":"{{ unique }}", "queries":[{"query":"@test:true","aggregation":"count","groupByFields":[],"distinctFields":[],"metric":""}],"filters":[],"cases":[{"name":"","status":"info","condition":"a > 0","notifications":[]}],"options":{"evaluationWindow":900,"keepAlive":3600,"maxSignalDuration":86400},"message":"Test rule","tags":[],"isEnabled":true, "type":"log_detection"}
7978
When the request is sent
8079
Then the response status is 200 OK
@@ -96,8 +95,7 @@ Feature: Security Monitoring
9695

9796
@team:DataDog/k9-cloud-security-platform
9897
Scenario: Convert an existing rule from JSON to Terraform returns "OK" response
99-
Given operation "ConvertExistingSecurityMonitoringRule" enabled
100-
And new "ConvertExistingSecurityMonitoringRule" request
98+
Given new "ConvertExistingSecurityMonitoringRule" request
10199
And there is a valid "security_rule" in the system
102100
And request contains "rule_id" parameter from "security_rule.id"
103101
When the request is sent

0 commit comments

Comments
 (0)