chore(spec): add missing descriptions [asm-backend]

.generator/schemas/v2/openapi.yaml

@@ -3988,6 +3988,7 @@ components:
         key_path:
           description: Specific path for the input.
           items:
+            description: A path segment for the input key.
             type: string
           type: array
       required:
@@ -4103,6 +4104,7 @@ components:
 
             !exact_match operator.'
           items:
+            description: A value to match against in the condition.
             type: string
           type: array
         options:
@@ -4379,6 +4381,8 @@ components:
           description: The client IP addresses matched by the exclusion filter (CIDR
             notation is supported).
           items:
+            description: A client IP address or CIDR range matched by the exclusion
+              filter.
             example: 198.51.100.72
             type: string
           type: array
@@ -4391,6 +4395,8 @@ components:
             HTTP query string and HTTP request body. Nested parameters can be matched
             by joining fields with a dot character.
           items:
+            description: A parameter name matched by the exclusion filter in the HTTP
+              query string or request body.
             example: list.search.query
             type: string
           type: array
@@ -4429,6 +4435,8 @@ components:
           description: The client IP addresses matched by the exclusion filter (CIDR
             notation is supported).
           items:
+            description: A client IP address or CIDR range matched by the exclusion
+              filter.
             example: 198.51.100.72
             type: string
           type: array
@@ -4439,6 +4447,8 @@ components:
             HTTP query string and HTTP request body. Nested parameters can be matched
             by joining fields with a dot character.
           items:
+            description: A parameter name matched by the exclusion filter in the HTTP
+              query string or request body.
             example: list.search.query
             type: string
           type: array
@@ -4594,6 +4604,8 @@ components:
           description: The client IP addresses matched by the exclusion filter (CIDR
             notation is supported).
           items:
+            description: A client IP address or CIDR range matched by the exclusion
+              filter.
             example: 198.51.100.72
             type: string
           type: array
@@ -4604,6 +4616,8 @@ components:
             HTTP query string and HTTP request body. Nested parameters can be matched
             by joining fields with a dot character.
           items:
+            description: A parameter name matched by the exclusion filter in the HTTP
+              query string or request body.
             example: list.search.query
             type: string
           type: array
@@ -44821,7 +44835,7 @@ components:
         Protocol (OTLP) over gRPC and HTTP.
 
 
-        **Supported pipeline types:** logs, metrics'
+        **Supported pipeline types:** logs'
       properties:
         grpc_address_key:
           description: Environment variable name containing the gRPC server address
@@ -44851,7 +44865,6 @@ components:
       type: object
       x-pipeline-types:
       - logs
-      - metrics
     ObservabilityPipelineOpentelemetrySourceType:
       default: opentelemetry
       description: The source type. The value should always be `opentelemetry`.

src/main/java/com/datadog/api/client/v2/model/ObservabilityPipelineOpentelemetrySource.java

@@ -21,7 +21,7 @@
  * The <code>opentelemetry</code> source receives telemetry data using the OpenTelemetry Protocol
  * (OTLP) over gRPC and HTTP.
  *
- * <p><strong>Supported pipeline types:</strong> logs, metrics
+ * <p><strong>Supported pipeline types:</strong> logs
  */
 @JsonPropertyOrder({
   ObservabilityPipelineOpentelemetrySource.JSON_PROPERTY_GRPC_ADDRESS_KEY,

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

@@ -149,14 +149,6 @@ Feature: Observability Pipelines
     And the response "data.attributes.config.destinations" has length 1
     And the response "data.attributes.config.destinations[0].id" is equal to "updated-datadog-logs-destination-id"
 
-  @team:DataDog/observability-pipelines
-  Scenario: Validate a metrics pipeline with opentelemetry source returns "OK" response
-    Given new "ValidatePipeline" request
-    And body with value {"data": {"attributes": {"config": {"pipeline_type": "metrics", "destinations": [{"id": "datadog-metrics-destination", "inputs": ["my-processor-group"], "type": "datadog_metrics"}], "processor_groups": [{"enabled": true, "id": "my-processor-group", "include": "*", "inputs": ["opentelemetry-source"], "processors": [{"enabled": true, "id": "filter-processor", "include": "env:production", "type": "filter"}]}], "sources": [{"id": "opentelemetry-source", "type": "opentelemetry"}]}, "name": "Metrics OTel Pipeline"}, "type": "pipelines"}}
-    When the request is sent
-    Then the response status is 200 OK
-    And the response "errors" has length 0
-
   @team:DataDog/observability-pipelines
   Scenario: Validate an observability pipeline returns "Bad Request" response
     Given new "ValidatePipeline" request