Regenerate client from commit 19796bd of spec repo

ci.datadog-api-spec · ci.datadog-api-spec · commit 48d278566bb7 · 2026-07-06T21:05:59.000Z
diff --git a/tests/v2/cassettes/test_scenarios/test_list_assets_sboms_returns_bad_request_invalid_pagination_token_response.frozen b/tests/v2/cassettes/test_scenarios/test_list_assets_sboms_returns_bad_request_invalid_pagination_token_response.frozen
@@ -0,0 +1 @@
+2026-07-06T19:25:16.964Z
diff --git a/tests/v2/cassettes/test_scenarios/test_list_assets_sboms_returns_bad_request_invalid_pagination_token_response.yaml b/tests/v2/cassettes/test_scenarios/test_list_assets_sboms_returns_bad_request_invalid_pagination_token_response.yaml
@@ -8,11 +8,12 @@ interactions:
     uri: https://api.datadoghq.com/api/v2/security/sboms?page%5Btoken%5D=unknown&page%5Bnumber%5D=1
   response:
     body:
-      string: '{"errors":[{"status":"404","title":"Unexpected internal error"}]}'
+      string: '{"errors":[{"status":"400","title":"Bad request: asset_type","detail":"asset_type
+        filter is required"}]}'
     headers:
       content-type:
       - application/vnd.api+json
     status:
-      code: 404
-      message: Not Found
+      code: 400
+      message: Bad Request
 version: 1
diff --git a/tests/v2/cassettes/test_scenarios/test_list_assets_sboms_returns_not_found_there_is_no_request_associated_with_the_provided_token_response.frozen b/tests/v2/cassettes/test_scenarios/test_list_assets_sboms_returns_not_found_there_is_no_request_associated_with_the_provided_token_response.frozen
diff --git a/tests/v2/cassettes/test_scenarios/test_list_scanned_assets_metadata_returns_bad_request_invalid_pagination_token_response.frozen b/tests/v2/cassettes/test_scenarios/test_list_scanned_assets_metadata_returns_bad_request_invalid_pagination_token_response.frozen
@@ -0,0 +1 @@
+2026-07-06T19:25:17.066Z
diff --git a/tests/v2/cassettes/test_scenarios/test_list_scanned_assets_metadata_returns_bad_request_invalid_pagination_token_response.yaml b/tests/v2/cassettes/test_scenarios/test_list_scanned_assets_metadata_returns_bad_request_invalid_pagination_token_response.yaml
@@ -8,11 +8,11 @@ interactions:
     uri: https://api.datadoghq.com/api/v2/security/scanned-assets-metadata?page%5Btoken%5D=unknown&page%5Bnumber%5D=1
   response:
     body:
-      string: '{"errors":[{"status":"404","title":"Unexpected internal error"}]}'
+      string: '{"errors":[{"status":"400","title":"Unexpected internal error"}]}'
     headers:
       content-type:
       - application/vnd.api+json
     status:
-      code: 404
-      message: Not Found
+      code: 400
+      message: Bad Request
 version: 1
diff --git a/tests/v2/cassettes/test_scenarios/test_list_scanned_assets_metadata_returns_not_found_asset_not_found_response.frozen b/tests/v2/cassettes/test_scenarios/test_list_scanned_assets_metadata_returns_not_found_asset_not_found_response.frozen
diff --git a/tests/v2/cassettes/test_scenarios/test_list_vulnerabilities_returns_bad_request_invalid_pagination_token_response.frozen b/tests/v2/cassettes/test_scenarios/test_list_vulnerabilities_returns_bad_request_invalid_pagination_token_response.frozen
@@ -0,0 +1 @@
+2026-07-06T19:25:19.361Z
diff --git a/tests/v2/cassettes/test_scenarios/test_list_vulnerabilities_returns_bad_request_invalid_pagination_token_response.yaml b/tests/v2/cassettes/test_scenarios/test_list_vulnerabilities_returns_bad_request_invalid_pagination_token_response.yaml
@@ -8,11 +8,11 @@ interactions:
     uri: https://api.datadoghq.com/api/v2/security/vulnerabilities?page%5Btoken%5D=unknown&page%5Bnumber%5D=1
   response:
     body:
-      string: '{"errors":[{"status":"404","title":"Unexpected internal error"}]}'
+      string: '{"errors":[{"status":"400","title":"Unexpected internal error"}]}'
     headers:
       content-type:
       - application/vnd.api+json
     status:
-      code: 404
-      message: Not Found
+      code: 400
+      message: Bad Request
 version: 1
diff --git a/tests/v2/cassettes/test_scenarios/test_list_vulnerabilities_returns_not_found_there_is_no_request_associated_with_the_provided_token_response.frozen b/tests/v2/cassettes/test_scenarios/test_list_vulnerabilities_returns_not_found_there_is_no_request_associated_with_the_provided_token_response.frozen
diff --git a/tests/v2/cassettes/test_scenarios/test_list_vulnerable_assets_returns_bad_request_invalid_pagination_token_response.frozen b/tests/v2/cassettes/test_scenarios/test_list_vulnerable_assets_returns_bad_request_invalid_pagination_token_response.frozen
@@ -0,0 +1 @@
+2026-07-06T19:25:22.396Z
diff --git a/tests/v2/cassettes/test_scenarios/test_list_vulnerable_assets_returns_bad_request_invalid_pagination_token_response.yaml b/tests/v2/cassettes/test_scenarios/test_list_vulnerable_assets_returns_bad_request_invalid_pagination_token_response.yaml
@@ -8,11 +8,11 @@ interactions:
     uri: https://api.datadoghq.com/api/v2/security/vulnerable-assets?page%5Btoken%5D=unknown&page%5Bnumber%5D=1
   response:
     body:
-      string: '{"errors":[{"status":"404","title":"Unexpected internal error"}]}'
+      string: '{"errors":[{"status":"400","title":"Unexpected internal error"}]}'
     headers:
       content-type:
       - application/vnd.api+json
     status:
-      code: 404
-      message: Not Found
+      code: 400
+      message: Bad Request
 version: 1
diff --git a/tests/v2/cassettes/test_scenarios/test_list_vulnerable_assets_returns_not_found_there_is_no_request_associated_with_the_provided_token_response.frozen b/tests/v2/cassettes/test_scenarios/test_list_vulnerable_assets_returns_not_found_there_is_no_request_associated_with_the_provided_token_response.frozen
diff --git a/tests/v2/features/security_monitoring.feature b/tests/v2/features/security_monitoring.feature
@@ -2318,19 +2318,19 @@ Feature: Security Monitoring
     When the request is sent
     Then the response status is 200 Vulnerabilities accepted successfully.
 
-  @generated @skip @team:DataDog/k9-cloud-vm
-  Scenario: List assets SBOMs returns "Bad request: The server cannot process the request due to invalid syntax in the request." response
-    Given new "ListAssetsSBOMs" request
-    When the request is sent
-    Then the response status is 400 Bad request: The server cannot process the request due to invalid syntax in the request.
-
   @team:DataDog/k9-cloud-vm
-  Scenario: List assets SBOMs returns "Not found: There is no request associated with the provided token." response
+  Scenario: List assets SBOMs returns "Bad request: Invalid pagination token." response
     Given new "ListAssetsSBOMs" request
     And request contains "page[token]" parameter with value "unknown"
     And request contains "page[number]" parameter with value 1
     When the request is sent
-    Then the response status is 404 Not found: There is no request associated with the provided token.
+    Then the response status is 400 Bad request: Invalid pagination token.
+
+  @generated @skip @team:DataDog/k9-cloud-vm
+  Scenario: List assets SBOMs returns "Bad request: The server cannot process the request due to invalid syntax in the request." response
+    Given new "ListAssetsSBOMs" request
+    When the request is sent
+    Then the response status is 400 Bad request: The server cannot process the request due to invalid syntax in the request.
 
   @generated @skip @team:DataDog/k9-cloud-vm
   Scenario: List assets SBOMs returns "Not found: asset not found" response
@@ -2504,19 +2504,26 @@ Feature: Security Monitoring
     When the request is sent
     Then the response status is 200 OK
 
+  @team:DataDog/k9-cloud-vm
+  Scenario: List scanned assets metadata returns "Bad request: Invalid Pagination Token" response
+    Given operation "ListScannedAssetsMetadata" enabled
+    And new "ListScannedAssetsMetadata" request
+    And request contains "page[token]" parameter with value "unknown"
+    And request contains "page[number]" parameter with value 1
+    When the request is sent
+    Then the response status is 400 Bad request: Invalid pagination token.
+
   @skip @team:DataDog/k9-cloud-vm
   Scenario: List scanned assets metadata returns "Bad request: The server cannot process the request due to invalid syntax in the request." response
     Given operation "ListScannedAssetsMetadata" enabled
     And new "ListScannedAssetsMetadata" request
     When the request is sent
     Then the response status is 400 Bad request: The server cannot process the request due to invalid syntax in the request.
 
-  @team:DataDog/k9-cloud-vm
+  @generated @skip @team:DataDog/k9-cloud-vm
   Scenario: List scanned assets metadata returns "Not found: asset not found" response
     Given operation "ListScannedAssetsMetadata" enabled
     And new "ListScannedAssetsMetadata" request
-    And request contains "page[token]" parameter with value "unknown"
-    And request contains "page[number]" parameter with value 1
     When the request is sent
     Then the response status is 404 Not found: asset not found
 
@@ -2550,19 +2557,26 @@ Feature: Security Monitoring
     And the response "meta.page" has field "after"
     And the response "links" has field "next"
 
+  @team:DataDog/k9-cloud-vm
+  Scenario: List vulnerabilities returns "Bad request: Invalid pagination token." response
+    Given operation "ListVulnerabilities" enabled
+    And new "ListVulnerabilities" request
+    And request contains "page[token]" parameter with value "unknown"
+    And request contains "page[number]" parameter with value 1
+    When the request is sent
+    Then the response status is 400 Bad request: Invalid pagination token.
+
   @generated @skip @team:DataDog/k9-cloud-vm
   Scenario: List vulnerabilities returns "Bad request: The server cannot process the request due to invalid syntax in the request." response
     Given operation "ListVulnerabilities" enabled
     And new "ListVulnerabilities" request
     When the request is sent
     Then the response status is 400 Bad request: The server cannot process the request due to invalid syntax in the request.
 
-  @team:DataDog/k9-cloud-vm
+  @generated @skip @team:DataDog/k9-cloud-vm
   Scenario: List vulnerabilities returns "Not found: There is no request associated with the provided token." response
     Given operation "ListVulnerabilities" enabled
     And new "ListVulnerabilities" request
-    And request contains "page[token]" parameter with value "unknown"
-    And request contains "page[number]" parameter with value 1
     When the request is sent
     Then the response status is 404 Not found: There is no request associated with the provided token.
 
@@ -2576,19 +2590,26 @@ Feature: Security Monitoring
     When the request is sent
     Then the response status is 200 OK
 
+  @team:DataDog/k9-cloud-vm
+  Scenario: List vulnerable assets returns "Bad request: Invalid Pagination Token" response
+    Given operation "ListVulnerableAssets" enabled
+    And new "ListVulnerableAssets" request
+    And request contains "page[token]" parameter with value "unknown"
+    And request contains "page[number]" parameter with value 1
+    When the request is sent
+    Then the response status is 400 Bad request: Invalid pagination token.
+
   @generated @skip @team:DataDog/k9-cloud-vm
   Scenario: List vulnerable assets returns "Bad request: The server cannot process the request due to invalid syntax in the request." response
     Given operation "ListVulnerableAssets" enabled
     And new "ListVulnerableAssets" request
     When the request is sent
     Then the response status is 400 Bad request: The server cannot process the request due to invalid syntax in the request.
 
-  @team:DataDog/k9-cloud-vm
+  @generated @skip @team:DataDog/k9-cloud-vm
   Scenario: List vulnerable assets returns "Not found: There is no request associated with the provided token." response
     Given operation "ListVulnerableAssets" enabled
     And new "ListVulnerableAssets" request
-    And request contains "page[token]" parameter with value "unknown"
-    And request contains "page[number]" parameter with value 1
     When the request is sent
     Then the response status is 404 Not found: There is no request associated with the provided token.
 
