Regenerate client from commit c16f550c of spec repo (#1066)

Co-authored-by: ci.datadog-api-spec <packages@datadoghq.com>

Author: api-clients-generation-pipeline[bot]

.apigentools-info

@@ -4,13 +4,13 @@
     "spec_versions": {
         "v1": {
             "apigentools_version": "1.6.2",
-            "regenerated": "2022-06-23 07:34:01.303866",
-            "spec_repo_commit": "c2c6e7b4"
+            "regenerated": "2022-06-23 08:09:34.821888",
+            "spec_repo_commit": "c16f550c"
         },
         "v2": {
             "apigentools_version": "1.6.2",
-            "regenerated": "2022-06-23 07:34:01.317476",
-            "spec_repo_commit": "c2c6e7b4"
+            "regenerated": "2022-06-23 08:09:34.834152",
+            "spec_repo_commit": "c16f550c"
         }
     }
 }

tests/v1/features/security_monitoring.feature

@@ -7,71 +7,71 @@ Feature: Security Monitoring
     And a valid "appKeyAuth" key in the system
     And an instance of "SecurityMonitoring" API
 
-  @generated @skip @team:DataDog/security-monitoring
+  @generated @skip @team:DataDog/k9-cloud-security-platform
   Scenario: Add a security signal to an incident returns "Bad Request" response
     Given new "AddSecurityMonitoringSignalToIncident" request
     And request contains "signal_id" parameter from "REPLACE.ME"
     And body with value {"incident_id": 2066}
     When the request is sent
     Then the response status is 400 Bad Request
 
-  @generated @skip @team:DataDog/security-monitoring
+  @generated @skip @team:DataDog/k9-cloud-security-platform
   Scenario: Add a security signal to an incident returns "Not Found" response
     Given new "AddSecurityMonitoringSignalToIncident" request
     And request contains "signal_id" parameter from "REPLACE.ME"
     And body with value {"incident_id": 2066}
     When the request is sent
     Then the response status is 404 Not Found
 
-  @replay-only @team:DataDog/security-monitoring
+  @replay-only @team:DataDog/k9-cloud-security-platform
   Scenario: Add a security signal to an incident returns "OK" response
     Given new "AddSecurityMonitoringSignalToIncident" request
     And request contains "signal_id" parameter with value "AQAAAYDiB_Ol8PbzFAAAAABBWURpQl9PbEFBQU0yeXhGTG9ZV2JnQUE"
     And body with value {"incident_id": 2609}
     When the request is sent
     Then the response status is 200 OK
 
-  @generated @skip @team:DataDog/security-monitoring
+  @generated @skip @team:DataDog/k9-cloud-security-platform
   Scenario: Change the triage state of a security signal returns "Bad Request" response
     Given new "EditSecurityMonitoringSignalState" request
     And request contains "signal_id" parameter from "REPLACE.ME"
     And body with value {"archiveReason": "none", "state": "open"}
     When the request is sent
     Then the response status is 400 Bad Request
 
-  @generated @skip @team:DataDog/security-monitoring
+  @generated @skip @team:DataDog/k9-cloud-security-platform
   Scenario: Change the triage state of a security signal returns "Not Found" response
     Given new "EditSecurityMonitoringSignalState" request
     And request contains "signal_id" parameter from "REPLACE.ME"
     And body with value {"archiveReason": "none", "state": "open"}
     When the request is sent
     Then the response status is 404 Not Found
 
-  @replay-only @team:DataDog/security-monitoring
+  @replay-only @team:DataDog/k9-cloud-security-platform
   Scenario: Change the triage state of a security signal returns "OK" response
     Given new "EditSecurityMonitoringSignalState" request
     And request contains "signal_id" parameter with value "AQAAAYDiB_Ol8PbzFAAAAABBWURpQl9PbEFBQU0yeXhGTG9ZV2JnQUE"
     And body with value {"archiveReason": "none", "state": "open"}
     When the request is sent
     Then the response status is 200 OK
 
-  @generated @skip @team:DataDog/security-monitoring
+  @generated @skip @team:DataDog/k9-cloud-security-platform
   Scenario: Modify the triage assignee of a security signal returns "Bad Request" response
     Given new "EditSecurityMonitoringSignalAssignee" request
     And request contains "signal_id" parameter from "REPLACE.ME"
     And body with value {"assignee": "773b045d-ccf8-4808-bd3b-955ef6a8c940"}
     When the request is sent
     Then the response status is 400 Bad Request
 
-  @generated @skip @team:DataDog/security-monitoring
+  @generated @skip @team:DataDog/k9-cloud-security-platform
   Scenario: Modify the triage assignee of a security signal returns "Not Found" response
     Given new "EditSecurityMonitoringSignalAssignee" request
     And request contains "signal_id" parameter from "REPLACE.ME"
     And body with value {"assignee": "773b045d-ccf8-4808-bd3b-955ef6a8c940"}
     When the request is sent
     Then the response status is 404 Not Found
 
-  @replay-only @team:DataDog/security-monitoring
+  @replay-only @team:DataDog/k9-cloud-security-platform
   Scenario: Modify the triage assignee of a security signal returns "OK" response
     Given new "EditSecurityMonitoringSignalAssignee" request
     And request contains "signal_id" parameter with value "AQAAAYDiB_Ol8PbzFAAAAABBWURpQl9PbEFBQU0yeXhGTG9ZV2JnQUE"

tests/v2/features/cloud_workload_security.feature

@@ -8,21 +8,21 @@ Feature: Cloud Workload Security
     And a valid "appKeyAuth" key in the system
     And an instance of "CloudWorkloadSecurity" API
 
-  @team:DataDog/cws-backend @team:DataDog/security-monitoring
+  @team:DataDog/cws-backend @team:DataDog/k9-cloud-security-platform
   Scenario: Create a Cloud Workload Security Agent rule returns "Bad Request" response
     Given new "CreateCloudWorkloadSecurityAgentRule" request
     And body with value {"data": {"attributes": {"description": "Test Agent rule", "enabled": true, "expression": "open.file.path = sh", "name": "{{ unique_lower_alnum }}"}, "type": "agent_rule"}}
     When the request is sent
     Then the response status is 400 Bad Request
 
-  @skip @team:DataDog/cws-backend @team:DataDog/security-monitoring
+  @skip @team:DataDog/cws-backend @team:DataDog/k9-cloud-security-platform
   Scenario: Create a Cloud Workload Security Agent rule returns "Conflict" response
     Given new "CreateCloudWorkloadSecurityAgentRule" request
     And body with value {"data": {"attributes": {"description": "Test Agent rule", "enabled": true, "expression": "exec.file.name == \"sh\"", "name": "{{ unique_lower_alnum }}"}, "type": "agent_rule"}}
     When the request is sent
     Then the response status is 409 Conflict
 
-  @team:DataDog/cws-backend @team:DataDog/security-monitoring
+  @team:DataDog/cws-backend @team:DataDog/k9-cloud-security-platform
   Scenario: Create a Cloud Workload Security Agent rule returns "OK" response
     Given new "CreateCloudWorkloadSecurityAgentRule" request
     And body with value {"data": {"attributes": {"description": "Test Agent rule", "enabled": true, "expression": "exec.file.name == \"sh\"", "name": "{{ unique_lower_alnum }}"}, "type": "agent_rule"}}
@@ -31,29 +31,29 @@ Feature: Cloud Workload Security
     And the response "data.type" is equal to "agent_rule"
     And the response "data.attributes.description" is equal to "Test Agent rule"
 
-  @team:DataDog/cws-backend @team:DataDog/security-monitoring
+  @team:DataDog/cws-backend @team:DataDog/k9-cloud-security-platform
   Scenario: Delete a Cloud Workload Security Agent rule returns "Not Found" response
     Given new "DeleteCloudWorkloadSecurityAgentRule" request
     And request contains "agent_rule_id" parameter with value "abc-123-xyz"
     When the request is sent
     Then the response status is 404 Not Found
 
-  @team:DataDog/cws-backend @team:DataDog/security-monitoring
+  @team:DataDog/cws-backend @team:DataDog/k9-cloud-security-platform
   Scenario: Delete a Cloud Workload Security Agent rule returns "OK" response
     Given there is a valid "agent_rule" in the system
     And new "DeleteCloudWorkloadSecurityAgentRule" request
     And request contains "agent_rule_id" parameter from "agent_rule.data.id"
     When the request is sent
     Then the response status is 204 OK
 
-  @team:DataDog/cws-backend @team:DataDog/security-monitoring
+  @team:DataDog/cws-backend @team:DataDog/k9-cloud-security-platform
   Scenario: Get a Cloud Workload Security Agent rule returns "Not Found" response
     Given new "GetCloudWorkloadSecurityAgentRule" request
     And request contains "agent_rule_id" parameter with value "abc-123-xyz"
     When the request is sent
     Then the response status is 404 Not Found
 
-  @team:DataDog/cws-backend @team:DataDog/security-monitoring
+  @team:DataDog/cws-backend @team:DataDog/k9-cloud-security-platform
   Scenario: Get a Cloud Workload Security Agent rule returns "OK" response
     Given there is a valid "agent_rule" in the system
     And new "GetCloudWorkloadSecurityAgentRule" request
@@ -63,21 +63,21 @@ Feature: Cloud Workload Security
     And the response "data.type" is equal to "agent_rule"
     And the response "data.attributes.description" is equal to "My Agent rule"
 
-  @team:DataDog/cws-backend @team:DataDog/security-monitoring
+  @team:DataDog/cws-backend @team:DataDog/k9-cloud-security-platform
   Scenario: Get all Cloud Workload Security Agent rules returns "OK" response
     Given there is a valid "agent_rule" in the system
     And new "ListCloudWorkloadSecurityAgentRules" request
     When the request is sent
     Then the response status is 200 OK
     And the response "data[0].type" is equal to "agent_rule"
 
-  @team:DataDog/cws-backend @team:DataDog/security-monitoring
+  @team:DataDog/cws-backend @team:DataDog/k9-cloud-security-platform
   Scenario: Get the latest Cloud Workload Security policy returns "OK" response
     Given new "DownloadCloudWorkloadPolicyFile" request
     When the request is sent
     Then the response status is 200 OK
 
-  @team:DataDog/cws-backend @team:DataDog/security-monitoring
+  @team:DataDog/cws-backend @team:DataDog/k9-cloud-security-platform
   Scenario: Update a Cloud Workload Security Agent rule returns "Bad Request" response
     Given there is a valid "agent_rule" in the system
     And new "UpdateCloudWorkloadSecurityAgentRule" request
@@ -86,7 +86,7 @@ Feature: Cloud Workload Security
     When the request is sent
     Then the response status is 400 Bad Request
 
-  @skip @team:DataDog/cws-backend @team:DataDog/security-monitoring
+  @skip @team:DataDog/cws-backend @team:DataDog/k9-cloud-security-platform
   Scenario: Update a Cloud Workload Security Agent rule returns "Concurrent Modification" response
     Given there is a valid "agent_rule" in the system
     And new "UpdateCloudWorkloadSecurityAgentRule" request
@@ -95,15 +95,15 @@ Feature: Cloud Workload Security
     When the request is sent
     Then the response status is 409 Concurrent Modification
 
-  @team:DataDog/cws-backend @team:DataDog/security-monitoring
+  @team:DataDog/cws-backend @team:DataDog/k9-cloud-security-platform
   Scenario: Update a Cloud Workload Security Agent rule returns "Not Found" response
     Given new "UpdateCloudWorkloadSecurityAgentRule" request
     And request contains "agent_rule_id" parameter with value "abc-123-xyz"
     And body with value {"data": {"attributes": {"description": "Test Agent rule", "enabled": true, "expression": "exec.file.name == \"sh\""}, "type": "agent_rule"}}
     When the request is sent
     Then the response status is 404 Not Found
 
-  @team:DataDog/cws-backend @team:DataDog/security-monitoring
+  @team:DataDog/cws-backend @team:DataDog/k9-cloud-security-platform
   Scenario: Update a Cloud Workload Security Agent rule returns "OK" response
     Given there is a valid "agent_rule" in the system
     And new "UpdateCloudWorkloadSecurityAgentRule" request