chore(spec): add missing descriptions [k9-cloud-vm]

.generator/schemas/v2/openapi.yaml

@@ -5548,6 +5548,7 @@ components:
           example:
           - staging
           items:
+            description: An environment where the asset is deployed.
             example: staging
             type: string
           type: array
@@ -5564,6 +5565,7 @@ components:
           example:
           - compute
           items:
+            description: A team that owns the asset.
             example: compute
             type: string
           type: array
@@ -36231,6 +36233,7 @@ components:
           description: Related library or package names (such as child packages or
             affected binary paths).
           items:
+            description: A related library or package name affected by the vulnerability.
             example: linux-tools-common
             type: string
           type: array
@@ -44821,7 +44824,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 +44854,6 @@ components:
       type: object
       x-pipeline-types:
       - logs
-      - metrics
     ObservabilityPipelineOpentelemetrySourceType:
       default: opentelemetry
       description: The source type. The value should always be `opentelemetry`.
@@ -55465,6 +55467,7 @@ components:
         dependsOn:
           description: The components that are dependencies of the ref component.
           items:
+            description: A package URL (purl) identifying a dependency of the component.
             example: pkg:golang/google.golang.org/grpc@1.68.1
             type: string
           required:
@@ -56079,6 +56082,8 @@ components:
           example:
           - production
           items:
+            description: An origin identifier for the last successful scan of the
+              asset.
             example: production
             type: string
           type: array
@@ -71815,6 +71820,7 @@ components:
           example:
           - CVE-2023-0615
           items:
+            description: A CVE identifier associated with the vulnerability.
             example: CVE-2023-0615
             type: string
           type: array
@@ -71865,6 +71871,8 @@ components:
           example:
           - agentless-scanner
           items:
+            description: The detection origin of the vulnerability (for example, the
+              scanner type).
             example: agentless-scanner
             type: string
           type: array
@@ -71877,6 +71885,8 @@ components:
           description: Vulnerability `repo_digest` list (when the vulnerability is
             related to `Image` asset).
           items:
+            description: A container image repository digest identifying the affected
+              image.
             example: sha256:0ae7da091191787229d321e3638e39c319a97d6e20f927d465b519d699215bf7
             type: string
           type: array
@@ -72018,6 +72028,7 @@ components:
           example:
           - NIST
           items:
+            description: An exploit source reporting this vulnerability.
             example: NIST
             type: string
           type: array

src/datadog_api_client/v2/model/observability_pipeline_opentelemetry_source.py

@@ -56,7 +56,7 @@ def __init__(
         """
         The ``opentelemetry`` source receives telemetry data using the OpenTelemetry Protocol (OTLP) over gRPC and HTTP.
 
-        **Supported pipeline types:** logs, metrics
+        **Supported pipeline types:** logs
 
         :param grpc_address_key: Environment variable name containing the gRPC server address for receiving OTLP data. Must be a valid environment variable name (alphanumeric characters and underscores only).
         :type grpc_address_key: str, optional

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