Regenerate client from commit 37cc6f3 of spec repo

Author: ci.datadog-api-spec

.generator/schemas/v2/openapi.yaml

@@ -0,0 +1 @@
+2025-10-14T13:09:10.481Z

cassettes/features/v2/security_monitoring/List-Scanned-Assets-Metadata-returns-Not-found-asset-not-found-response.frozen

@@ -0,0 +1 @@
+2025-10-14T13:14:21.010Z

cassettes/features/v2/security_monitoring/List-Scanned-Assets-Metadata-returns-Not-found-asset-not-found-response.yml

@@ -0,0 +1,8 @@
+# List Scanned Assets Metadata returns "OK" response
+
+require "datadog_api_client"
+DatadogAPIClient.configure do |config|
+  config.unstable_operations["v2.list_scanned_assets_metadata".to_sym] = true
+end
+api_instance = DatadogAPIClient::V2::SecurityMonitoringAPI.new
+p api_instance.list_scanned_assets_metadata()

cassettes/features/v2/security_monitoring/List-Scanned-Assets-Metadata-returns-OK-response.frozen

@@ -1313,6 +1313,15 @@
             "asset_type" => "AssetType",
             "filter_asset_name" => "String",
             "filter_repo_digest" => "String",
+            "ext_format" => "SBOMFormat",
+    },
+    "v2.ListScannedAssetsMetadata" => {
+            "page_token" => "String",
+            "page_number" => "Integer",
+            "filter_asset_type" => "CloudAssetType",
+            "filter_asset_name" => "String",
+            "filter_last_success_origin" => "String",
+            "filter_last_success_env" => "String",
     },
     "v2.CreateSignalNotificationRule" => {
             "body" => "CreateNotificationRuleParameters",

cassettes/features/v2/security_monitoring/List-Scanned-Assets-Metadata-returns-OK-response.yml

@@ -923,6 +923,29 @@ Feature: Security Monitoring
     When the request is sent
     Then the response status is 200 The list of notification rules.
 
+  @skip @team:DataDog/asm-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/asm-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
+
+  @team:DataDog/asm-vm
+  Scenario: List Scanned Assets Metadata returns "OK" response
+    Given operation "ListScannedAssetsMetadata" enabled
+    And new "ListScannedAssetsMetadata" request
+    When the request is sent
+    Then the response status is 200 OK
+
   @generated @skip @team:DataDog/asm-vm
   Scenario: List assets SBOMs returns "Bad request: The server cannot process the request due to invalid syntax in the request." response
     Given operation "ListAssetsSBOMs" enabled

examples/v2/security-monitoring/ListScannedAssetsMetadata.rb

@@ -3204,6 +3204,12 @@
       "type": "safe"
     }
   },
+  "ListScannedAssetsMetadata": {
+    "tag": "Security Monitoring",
+    "undo": {
+      "type": "safe"
+    }
+  },
   "GetSignalNotificationRules": {
     "tag": "Security Monitoring",
     "undo": {

features/scenarios_model_mapping.rb

@@ -206,6 +206,7 @@ def initialize
             "v2.list_assets_sbo_ms": false,
             "v2.list_findings": false,
             "v2.list_historical_jobs": false,
+            "v2.list_scanned_assets_metadata": false,
             "v2.list_security_monitoring_histsignals": false,
             "v2.list_vulnerabilities": false,
             "v2.list_vulnerable_assets": false,