chore(spec): add missing descriptions [sensitive-data-scanner]

.generator/schemas/v2/openapi.yaml

@@ -44821,7 +44821,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 +44851,6 @@ components:
       type: object
       x-pipeline-types:
       - logs
-      - metrics
     ObservabilityPipelineOpentelemetrySourceType:
       default: opentelemetry
       description: The source type. The value should always be `opentelemetry`.
@@ -60870,6 +60869,8 @@ components:
           - address
           - login
           items:
+            description: A keyword to match within the defined proximity of the detected
+              pattern.
             type: string
           type: array
         use_recommended_keywords:
@@ -60978,6 +60979,7 @@ components:
           example:
           - admin.name
           items:
+            description: An attribute path to exclude from the scan.
             type: string
           type: array
         included_keyword_configuration:
@@ -60996,6 +60998,7 @@ components:
           example:
           - admin
           items:
+            description: An attribute path to include in the scan.
             type: string
           type: array
         pattern:
@@ -61012,6 +61015,7 @@ components:
         tags:
           description: List of tags.
           items:
+            description: A tag associated with the rule.
             type: string
           type: array
         text_replacement:
@@ -61169,6 +61173,8 @@ components:
         included_keywords:
           description: List of included keywords.
           items:
+            description: A keyword used to increase match precision for the standard
+              pattern.
             type: string
           type: array
         name:
@@ -61190,6 +61196,7 @@ components:
         tags:
           description: List of tags.
           items:
+            description: A tag associated with the standard pattern.
             type: string
           type: array
       type: object
@@ -61244,6 +61251,7 @@ components:
           - '@example.com'
           - another.example.com
           items:
+            description: A string suffix; matches ending with this value are suppressed.
             type: string
           type: array
         exact_match:
@@ -61253,6 +61261,7 @@ components:
           - admin@example.com
           - user@example.com
           items:
+            description: A string value; matches exactly equal to this value are suppressed.
             type: string
           type: array
         starts_with:
@@ -61262,6 +61271,7 @@ components:
           - admin
           - user
           items:
+            description: A string prefix; matches starting with this value are suppressed.
             type: string
           type: array
       type: object

features/v2/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

lib/datadog_api_client/v2/models/observability_pipeline_opentelemetry_source.rb

@@ -19,7 +19,7 @@
 module DatadogAPIClient::V2
   # The `opentelemetry` source receives telemetry data using the OpenTelemetry Protocol (OTLP) over gRPC and HTTP.
   # 
-  # **Supported pipeline types:** logs, metrics
+  # **Supported pipeline types:** logs
   class ObservabilityPipelineOpentelemetrySource
     include BaseGenericModel