Skip to content

Commit 7e540cf

Browse files
author
ci.datadog-api-spec
committed
Regenerate client from commit 2ea314f of spec repo
1 parent 6eee8c8 commit 7e540cf

File tree

5 files changed

+228
-228
lines changed

5 files changed

+228
-228
lines changed

src/test/resources/com/datadog/api/client/v1/api/security_monitoring.feature

Lines changed: 9 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -9,23 +9,23 @@ Feature: Security Monitoring
99
And a valid "appKeyAuth" key in the system
1010
And an instance of "SecurityMonitoring" API
1111

12-
@generated @skip @team:DataDog/k9-cloud-security-platform
12+
@generated @skip @team:DataDog/k9-cloud-siem
1313
Scenario: Add a security signal to an incident returns "Bad Request" response
1414
Given new "AddSecurityMonitoringSignalToIncident" request
1515
And request contains "signal_id" parameter from "REPLACE.ME"
1616
And body with value {"incident_id": 2066, "version": 0}
1717
When the request is sent
1818
Then the response status is 400 Bad Request
1919

20-
@generated @skip @team:DataDog/k9-cloud-security-platform
20+
@generated @skip @team:DataDog/k9-cloud-siem
2121
Scenario: Add a security signal to an incident returns "Not Found" response
2222
Given new "AddSecurityMonitoringSignalToIncident" request
2323
And request contains "signal_id" parameter from "REPLACE.ME"
2424
And body with value {"incident_id": 2066, "version": 0}
2525
When the request is sent
2626
Then the response status is 404 Not Found
2727

28-
@replay-only @team:DataDog/k9-cloud-security-platform
28+
@replay-only @team:DataDog/k9-cloud-siem
2929
Scenario: Add a security signal to an incident returns "OK" response
3030
Given new "AddSecurityMonitoringSignalToIncident" request
3131
And request contains "signal_id" parameter with value "AQAAAYDiB_Ol8PbzFAAAAABBWURpQl9PbEFBQU0yeXhGTG9ZV2JnQUE"
@@ -34,23 +34,23 @@ Feature: Security Monitoring
3434
Then the response status is 200 OK
3535
And the response "status" is equal to "done"
3636

37-
@generated @skip @team:DataDog/k9-cloud-security-platform
37+
@generated @skip @team:DataDog/k9-cloud-siem
3838
Scenario: Change the triage state of a security signal returns "Bad Request" response
3939
Given new "EditSecurityMonitoringSignalState" request
4040
And request contains "signal_id" parameter from "REPLACE.ME"
4141
And body with value {"archiveReason": "none", "state": "open", "version": 0}
4242
When the request is sent
4343
Then the response status is 400 Bad Request
4444

45-
@generated @skip @team:DataDog/k9-cloud-security-platform
45+
@generated @skip @team:DataDog/k9-cloud-siem
4646
Scenario: Change the triage state of a security signal returns "Not Found" response
4747
Given new "EditSecurityMonitoringSignalState" request
4848
And request contains "signal_id" parameter from "REPLACE.ME"
4949
And body with value {"archiveReason": "none", "state": "open", "version": 0}
5050
When the request is sent
5151
Then the response status is 404 Not Found
5252

53-
@replay-only @team:DataDog/k9-cloud-security-platform
53+
@replay-only @team:DataDog/k9-cloud-siem
5454
Scenario: Change the triage state of a security signal returns "OK" response
5555
Given new "EditSecurityMonitoringSignalState" request
5656
And request contains "signal_id" parameter with value "AQAAAYDiB_Ol8PbzFAAAAABBWURpQl9PbEFBQU0yeXhGTG9ZV2JnQUE"
@@ -59,23 +59,23 @@ Feature: Security Monitoring
5959
Then the response status is 200 OK
6060
And the response "status" is equal to "done"
6161

62-
@generated @skip @team:DataDog/k9-cloud-security-platform
62+
@generated @skip @team:DataDog/k9-cloud-siem
6363
Scenario: Modify the triage assignee of a security signal returns "Bad Request" response
6464
Given new "EditSecurityMonitoringSignalAssignee" request
6565
And request contains "signal_id" parameter from "REPLACE.ME"
6666
And body with value {"assignee": "773b045d-ccf8-4808-bd3b-955ef6a8c940", "version": 0}
6767
When the request is sent
6868
Then the response status is 400 Bad Request
6969

70-
@generated @skip @team:DataDog/k9-cloud-security-platform
70+
@generated @skip @team:DataDog/k9-cloud-siem
7171
Scenario: Modify the triage assignee of a security signal returns "Not Found" response
7272
Given new "EditSecurityMonitoringSignalAssignee" request
7373
And request contains "signal_id" parameter from "REPLACE.ME"
7474
And body with value {"assignee": "773b045d-ccf8-4808-bd3b-955ef6a8c940", "version": 0}
7575
When the request is sent
7676
Then the response status is 404 Not Found
7777

78-
@replay-only @team:DataDog/k9-cloud-security-platform
78+
@replay-only @team:DataDog/k9-cloud-siem
7979
Scenario: Modify the triage assignee of a security signal returns "OK" response
8080
Given new "EditSecurityMonitoringSignalAssignee" request
8181
And request contains "signal_id" parameter with value "AQAAAYDiB_Ol8PbzFAAAAABBWURpQl9PbEFBQU0yeXhGTG9ZV2JnQUE"

src/test/resources/com/datadog/api/client/v2/api/csm_agents.feature

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -12,13 +12,13 @@ Feature: CSM Agents
1212
And a valid "appKeyAuth" key in the system
1313
And an instance of "CSMAgents" API
1414

15-
@team:DataDog/k9-cloud-security-platform
15+
@team:DataDog/k9-misconfigs
1616
Scenario: Get all CSM Agents returns "OK" response
1717
Given new "ListAllCSMAgents" request
1818
When the request is sent
1919
Then the response status is 200 OK
2020

21-
@team:DataDog/k9-cloud-security-platform
21+
@team:DataDog/k9-misconfigs
2222
Scenario: Get all CSM Serverless Agents returns "OK" response
2323
Given new "ListAllCSMServerlessAgents" request
2424
When the request is sent

src/test/resources/com/datadog/api/client/v2/api/csm_coverage_analysis.feature

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -12,19 +12,19 @@ Feature: CSM Coverage Analysis
1212
And a valid "appKeyAuth" key in the system
1313
And an instance of "CSMCoverageAnalysis" API
1414

15-
@team:DataDog/k9-cloud-security-platform
15+
@team:DataDog/k9-misconfigs
1616
Scenario: Get the CSM Cloud Accounts Coverage Analysis returns "OK" response
1717
Given new "GetCSMCloudAccountsCoverageAnalysis" request
1818
When the request is sent
1919
Then the response status is 200 OK
2020

21-
@team:DataDog/k9-cloud-security-platform
21+
@team:DataDog/k9-misconfigs
2222
Scenario: Get the CSM Hosts and Containers Coverage Analysis returns "OK" response
2323
Given new "GetCSMHostsAndContainersCoverageAnalysis" request
2424
When the request is sent
2525
Then the response status is 200 OK
2626

27-
@team:DataDog/k9-cloud-security-platform
27+
@team:DataDog/k9-misconfigs
2828
Scenario: Get the CSM Serverless Coverage Analysis returns "OK" response
2929
Given new "GetCSMServerlessCoverageAnalysis" request
3030
When the request is sent

0 commit comments

Comments
 (0)