Regenerate client from commit 9dfc165 of spec repo

ci.datadog-api-spec · ci.datadog-api-spec · commit 0bccc00e42cc · 2026-05-28T11:46:24.000Z
diff --git a/.generator/schemas/v2/openapi.yaml b/.generator/schemas/v2/openapi.yaml
@@ -55624,6 +55624,7 @@ components:
         - $ref: "#/components/schemas/ObservabilityPipelineSyslogNgDestination"
         - $ref: "#/components/schemas/ObservabilityPipelineDatabricksZerobusDestination"
         - $ref: "#/components/schemas/ObservabilityPipelineDatadogMetricsDestination"
+        - $ref: "#/components/schemas/ObservabilityPipelineSplunkHecMetricsDestination"
     ObservabilityPipelineConfigPipelineType:
       default: logs
       description: The type of data being ingested. Defaults to `logs` if not specified.
@@ -59745,6 +59746,81 @@ components:
       type: string
       x-enum-varnames:
         - SPLUNK_HEC
+    ObservabilityPipelineSplunkHecMetricsDestination:
+      description: |-
+        The `splunk_hec_metrics` destination forwards metrics to Splunk using the HTTP Event Collector (HEC).
+
+        **Supported pipeline types:** metrics
+      properties:
+        buffer:
+          $ref: "#/components/schemas/ObservabilityPipelineBufferOptions"
+        compression:
+          $ref: "#/components/schemas/ObservabilityPipelineSplunkHecMetricsDestinationCompression"
+        default_namespace:
+          description: Optional default namespace for metrics sent to Splunk HEC.
+          example: "custom_namespace"
+          type: string
+        endpoint_url_key:
+          description: Name of the environment variable or secret that holds the Splunk HEC endpoint URL.
+          example: SPLUNK_HEC_ENDPOINT_URL
+          type: string
+        id:
+          description: The unique identifier for this component. Used in other parts of the pipeline to reference this component (for example, as the `input` to downstream components).
+          example: splunk-hec-metrics-destination
+          type: string
+        index:
+          description: Optional name of the Splunk index where metrics are written.
+          example: "metrics"
+          type: string
+        inputs:
+          description: A list of component IDs whose output is used as the `input` for this component.
+          example: ["metrics-filter-processor"]
+          items:
+            description: The ID of a component whose output is used as input for this destination.
+            type: string
+          type: array
+        source:
+          description: The Splunk source field value for metric events.
+          example: "observability_pipelines"
+          type: string
+        sourcetype:
+          description: The Splunk sourcetype to assign to metric events.
+          example: "custom_sourcetype"
+          type: string
+        tls:
+          $ref: "#/components/schemas/ObservabilityPipelineTls"
+        token_key:
+          description: Name of the environment variable or secret that holds the Splunk HEC token.
+          example: SPLUNK_HEC_TOKEN
+          type: string
+        type:
+          $ref: "#/components/schemas/ObservabilityPipelineSplunkHecMetricsDestinationType"
+      required:
+        - id
+        - type
+        - inputs
+      type: object
+      x-pipeline-types: [metrics]
+    ObservabilityPipelineSplunkHecMetricsDestinationCompression:
+      default: none
+      description: Compression algorithm applied when sending metrics to Splunk HEC.
+      enum:
+        - none
+        - gzip
+      example: none
+      type: string
+      x-enum-varnames:
+        - NONE
+        - GZIP
+    ObservabilityPipelineSplunkHecMetricsDestinationType:
+      default: splunk_hec_metrics
+      description: The destination type. Always `splunk_hec_metrics`.
+      enum:
+        - splunk_hec_metrics
+      example: splunk_hec_metrics
+      type: string
+      x-enum-varnames:
+        - SPLUNK_HEC_METRICS
     ObservabilityPipelineSplunkHecSource:
       description: |-
         The `splunk_hec` source implements the Splunk HTTP Event Collector (HEC) API.
@@ -146686,9 +146762,6 @@ paths:
         permissions:
           - security_monitoring_findings_write
           - appsec_vm_write
-      x-unstable: |-
-        **Note**: This endpoint is in preview and is subject to change.
-        If you have any feedback, contact [Datadog support](https://docs.datadoghq.com/help/).
   /api/v2/security/findings/search:
     post:
       description: |-
diff --git a/examples/v2/security-monitoring/MuteSecurityFindings.rb b/examples/v2/security-monitoring/MuteSecurityFindings.rb
@@ -1,9 +1,6 @@
 # Mute or unmute security findings returns "Accepted" response
 
 require "datadog_api_client"
-DatadogAPIClient.configure do |config|
-  config.unstable_operations["v2.mute_security_findings".to_sym] = true
-end
 api_instance = DatadogAPIClient::V2::SecurityMonitoringAPI.new
 
 body = DatadogAPIClient::V2::MuteFindingsRequest.new({
diff --git a/examples/v2/security-monitoring/MuteSecurityFindings_298521544.rb b/examples/v2/security-monitoring/MuteSecurityFindings_298521544.rb
@@ -1,9 +1,6 @@
 # Unmute security findings returns "Accepted" response
 
 require "datadog_api_client"
-DatadogAPIClient.configure do |config|
-  config.unstable_operations["v2.mute_security_findings".to_sym] = true
-end
 api_instance = DatadogAPIClient::V2::SecurityMonitoringAPI.new
 
 body = DatadogAPIClient::V2::MuteFindingsRequest.new({
diff --git a/examples/v2/security-monitoring/MuteSecurityFindings_3830190821.rb b/examples/v2/security-monitoring/MuteSecurityFindings_3830190821.rb
@@ -1,9 +1,6 @@
 # Mute security findings returns "Accepted" response
 
 require "datadog_api_client"
-DatadogAPIClient.configure do |config|
-  config.unstable_operations["v2.mute_security_findings".to_sym] = true
-end
 api_instance = DatadogAPIClient::V2::SecurityMonitoringAPI.new
 
 body = DatadogAPIClient::V2::MuteFindingsRequest.new({
diff --git a/features/v2/security_monitoring.feature b/features/v2/security_monitoring.feature
@@ -2300,56 +2300,49 @@ Feature: Security Monitoring
 
   @generated @skip @team:DataDog/k9-investigation
   Scenario: Mute or unmute security findings returns "Accepted" response
-    Given operation "MuteSecurityFindings" enabled
-    And new "MuteSecurityFindings" request
+    Given new "MuteSecurityFindings" request
     And body with value {"data": {"attributes": {"mute": {"description": "To be resolved later.", "expire_at": 1778721573794, "is_muted": true, "reason": "PENDING_FIX"}}, "id": "00000000-0000-0000-0000-000000000001", "relationships": {"findings": {"data": [{"id": "ZGVmLTAwcC1pZXJ-aS0wZjhjNjMyZDNmMzRlZTgzNw==", "type": "findings"}]}}, "type": "mute"}}
     When the request is sent
     Then the response status is 202 Accepted
 
   @generated @skip @team:DataDog/k9-investigation
   Scenario: Mute or unmute security findings returns "Bad Request" response
-    Given operation "MuteSecurityFindings" enabled
-    And new "MuteSecurityFindings" request
+    Given new "MuteSecurityFindings" request
     And body with value {"data": {"attributes": {"mute": {"description": "To be resolved later.", "expire_at": 1778721573794, "is_muted": true, "reason": "PENDING_FIX"}}, "id": "00000000-0000-0000-0000-000000000001", "relationships": {"findings": {"data": [{"id": "ZGVmLTAwcC1pZXJ-aS0wZjhjNjMyZDNmMzRlZTgzNw==", "type": "findings"}]}}, "type": "mute"}}
     When the request is sent
     Then the response status is 400 Bad Request
 
   @generated @skip @team:DataDog/k9-investigation
   Scenario: Mute or unmute security findings returns "Not Found" response
-    Given operation "MuteSecurityFindings" enabled
-    And new "MuteSecurityFindings" request
+    Given new "MuteSecurityFindings" request
     And body with value {"data": {"attributes": {"mute": {"description": "To be resolved later.", "expire_at": 1778721573794, "is_muted": true, "reason": "PENDING_FIX"}}, "id": "00000000-0000-0000-0000-000000000001", "relationships": {"findings": {"data": [{"id": "ZGVmLTAwcC1pZXJ-aS0wZjhjNjMyZDNmMzRlZTgzNw==", "type": "findings"}]}}, "type": "mute"}}
     When the request is sent
     Then the response status is 404 Not Found
 
   @generated @skip @team:DataDog/k9-investigation
   Scenario: Mute or unmute security findings returns "Unprocessable Entity" response
-    Given operation "MuteSecurityFindings" enabled
-    And new "MuteSecurityFindings" request
+    Given new "MuteSecurityFindings" request
     And body with value {"data": {"attributes": {"mute": {"description": "To be resolved later.", "expire_at": 1778721573794, "is_muted": true, "reason": "PENDING_FIX"}}, "id": "00000000-0000-0000-0000-000000000001", "relationships": {"findings": {"data": [{"id": "ZGVmLTAwcC1pZXJ-aS0wZjhjNjMyZDNmMzRlZTgzNw==", "type": "findings"}]}}, "type": "mute"}}
     When the request is sent
     Then the response status is 422 Unprocessable Entity
 
   @team:DataDog/k9-investigation
   Scenario: Mute security findings returns "Accepted" response
-    Given operation "MuteSecurityFindings" enabled
-    And new "MuteSecurityFindings" request
+    Given new "MuteSecurityFindings" request
     And body with value {"data": {"attributes": {"mute": {"description": "To be resolved later.", "expire_at": 1778721573794, "is_muted": true, "reason": "RISK_ACCEPTED"}}, "relationships": {"findings": {"data": [{"id": "ZGVmLTAwMC0wYmd-MDE4NjcyMDJkMzE4MDE5ODY5MGE4ZmQ2MmFlMjg0Y2M=", "type": "findings"}]}}, "type": "mute"}}
     When the request is sent
     Then the response status is 202 Accepted
 
   @team:DataDog/k9-investigation
   Scenario: Mute security findings returns "Not Found" response
-    Given operation "MuteSecurityFindings" enabled
-    And new "MuteSecurityFindings" request
+    Given new "MuteSecurityFindings" request
     And body with value {"data": {"attributes": {"mute": {"description": "To be resolved later.", "expire_at": 1778721573794, "is_muted": true, "reason": "RISK_ACCEPTED"}}, "relationships": {"findings": {"data": [{"id": "ZGVmLTAwcC1pZXJ-aS0wZjhjNjMyZDNmMzRlZTgzNw==", "type": "findings"}]}}, "type": "mute"}}
     When the request is sent
     Then the response status is 404 Not Found
 
   @team:DataDog/k9-investigation
   Scenario: Mute security findings returns "Unprocessable Entity" response
-    Given operation "MuteSecurityFindings" enabled
-    And new "MuteSecurityFindings" request
+    Given new "MuteSecurityFindings" request
     And body with value {"data": {"attributes": {"mute": {"description": "To be resolved later.", "expire_at": 1, "is_muted": true, "reason": "RISK_ACCEPTED"}}, "relationships": {"findings": {"data": [{"id": "ZGVmLTAwcC1pZXJ-aS0wZjhjNjMyZDNmMzRlZTgzNw==", "type": "findings"}]}}, "type": "mute"}}
     When the request is sent
     Then the response status is 422 Unprocessable Entity
@@ -2573,24 +2566,21 @@ Feature: Security Monitoring
 
   @team:DataDog/k9-investigation
   Scenario: Unmute security findings returns "Accepted" response
-    Given operation "MuteSecurityFindings" enabled
-    And new "MuteSecurityFindings" request
+    Given new "MuteSecurityFindings" request
     And body with value {"data": {"attributes": {"mute": {"description": "Resolved.", "is_muted": false, "reason": "NO_PENDING_FIX"}}, "relationships": {"findings": {"data": [{"id": "ZGVmLTAwMC0wYmd-MDE4NjcyMDJkMzE4MDE5ODY5MGE4ZmQ2MmFlMjg0Y2M=", "type": "findings"}]}}, "type": "mute"}}
     When the request is sent
     Then the response status is 202 Accepted
 
   @team:DataDog/k9-investigation
   Scenario: Unmute security findings returns "Not Found" response
-    Given operation "MuteSecurityFindings" enabled
-    And new "MuteSecurityFindings" request
+    Given new "MuteSecurityFindings" request
     And body with value {"data": {"attributes": {"mute": {"description": "Resolved.", "is_muted": false, "reason": "NO_PENDING_FIX"}}, "relationships": {"findings": {"data": [{"id": "ZGVmLTAwcC1pZXJ-aS0wZjhjNjMyZDNmMzRlZTgzNw==", "type": "findings"}]}}, "type": "mute"}}
     When the request is sent
     Then the response status is 404 Not Found
 
   @team:DataDog/k9-investigation
   Scenario: Unmute security findings returns "Unprocessable Entity" response
-    Given operation "MuteSecurityFindings" enabled
-    And new "MuteSecurityFindings" request
+    Given new "MuteSecurityFindings" request
     And body with value {"data": {"attributes": {"mute": {"description": "Resolved.", "is_muted": false, "reason": "RISK_ACCEPTED"}}, "relationships": {"findings": {"data": [{"id": "ZGVmLTAwcC1pZXJ-aS0wZjhjNjMyZDNmMzRlZTgzNw==", "type": "findings"}]}}, "type": "mute"}}
     When the request is sent
     Then the response status is 422 Unprocessable Entity
diff --git a/lib/datadog_api_client/configuration.rb b/lib/datadog_api_client/configuration.rb
@@ -363,7 +363,6 @@ def initialize
             "v2.list_vulnerabilities": false,
             "v2.list_vulnerable_assets": false,
             "v2.mute_findings": false,
-            "v2.mute_security_findings": false,
             "v2.run_historical_job": false,
             "v2.search_security_monitoring_histsignals": false,
             "v2.update_security_monitoring_dataset": false,
diff --git a/lib/datadog_api_client/inflector.rb b/lib/datadog_api_client/inflector.rb
@@ -4732,6 +4732,9 @@ def overrides
           "v2.observability_pipeline_splunk_hec_destination_encoding" => "ObservabilityPipelineSplunkHecDestinationEncoding",
           "v2.observability_pipeline_splunk_hec_destination_token_strategy" => "ObservabilityPipelineSplunkHecDestinationTokenStrategy",
           "v2.observability_pipeline_splunk_hec_destination_type" => "ObservabilityPipelineSplunkHecDestinationType",
+          "v2.observability_pipeline_splunk_hec_metrics_destination" => "ObservabilityPipelineSplunkHecMetricsDestination",
+          "v2.observability_pipeline_splunk_hec_metrics_destination_compression" => "ObservabilityPipelineSplunkHecMetricsDestinationCompression",
+          "v2.observability_pipeline_splunk_hec_metrics_destination_type" => "ObservabilityPipelineSplunkHecMetricsDestinationType",
           "v2.observability_pipeline_splunk_hec_source" => "ObservabilityPipelineSplunkHecSource",
           "v2.observability_pipeline_splunk_hec_source_type" => "ObservabilityPipelineSplunkHecSourceType",
           "v2.observability_pipeline_splunk_hec_source_valid_token" => "ObservabilityPipelineSplunkHecSourceValidToken",
diff --git a/lib/datadog_api_client/v2/api/security_monitoring_api.rb b/lib/datadog_api_client/v2/api/security_monitoring_api.rb
@@ -8009,12 +8009,6 @@ def mute_security_findings(body, opts = {})
     # @param opts [Hash] the optional parameters
     # @return [Array<(MuteFindingsResponse, Integer, Hash)>] MuteFindingsResponse data, response status code and response headers
     def mute_security_findings_with_http_info(body, opts = {})
-      unstable_enabled = @api_client.config.unstable_operations["v2.mute_security_findings".to_sym]
-      if unstable_enabled
-        @api_client.config.logger.warn format("Using unstable operation '%s'", "v2.mute_security_findings")
-      else
-        raise DatadogAPIClient::APIError.new(message: format("Unstable operation '%s' is disabled", "v2.mute_security_findings"))
-      end
 
       if @api_client.config.debugging
         @api_client.config.logger.debug 'Calling API: SecurityMonitoringAPI.mute_security_findings ...'
diff --git a/lib/datadog_api_client/v2/models/observability_pipeline_config_destination_item.rb b/lib/datadog_api_client/v2/models/observability_pipeline_config_destination_item.rb
@@ -50,7 +50,8 @@ def openapi_one_of
           :'ObservabilityPipelineSumoLogicDestination',
           :'ObservabilityPipelineSyslogNgDestination',
           :'ObservabilityPipelineDatabricksZerobusDestination',
-          :'ObservabilityPipelineDatadogMetricsDestination'
+          :'ObservabilityPipelineDatadogMetricsDestination',
+          :'ObservabilityPipelineSplunkHecMetricsDestination'
         ]
       end
       # Builds the object
diff --git a/lib/datadog_api_client/v2/models/observability_pipeline_splunk_hec_metrics_destination.rb b/lib/datadog_api_client/v2/models/observability_pipeline_splunk_hec_metrics_destination.rb
diff --git a/lib/datadog_api_client/v2/models/observability_pipeline_splunk_hec_metrics_destination_compression.rb b/lib/datadog_api_client/v2/models/observability_pipeline_splunk_hec_metrics_destination_compression.rb
diff --git a/lib/datadog_api_client/v2/models/observability_pipeline_splunk_hec_metrics_destination_type.rb b/lib/datadog_api_client/v2/models/observability_pipeline_splunk_hec_metrics_destination_type.rb
