chore(spec): add missing descriptions [apm-aoe]

.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`.
@@ -62296,37 +62295,49 @@ components:
           type: array
       type: object
     ServiceList:
+      description: The response body for the service list endpoint.
       properties:
         data:
           $ref: '#/components/schemas/ServiceListData'
       type: object
     ServiceListData:
+      description: A single data item in the service list response.
       properties:
         attributes:
           $ref: '#/components/schemas/ServiceListDataAttributes'
         id:
+          description: The unique identifier of the service.
           type: string
         type:
           $ref: '#/components/schemas/ServiceListDataType'
       required:
       - type
       type: object
     ServiceListDataAttributes:
+      description: Attributes of a service list entry, containing metadata and a list
+        of service names.
       properties:
         metadata:
+          description: A list of metadata items associated with the service.
           items:
             $ref: '#/components/schemas/ServiceListDataAttributesMetadataItems'
           type: array
         services:
+          description: A list of service names.
           items:
+            description: A single service name.
             type: string
           type: array
       type: object
     ServiceListDataAttributesMetadataItems:
+      description: An object containing metadata flags for a service, indicating whether
+        it is traced by APM or monitored via Universal Service Monitoring.
       properties:
         isTraced:
+          description: Indicates whether the service is traced by APM.
           type: boolean
         isUsm:
+          description: Indicates whether the service uses Universal Service Monitoring.
           type: boolean
       type: object
     ServiceListDataType:

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

src/datadog_api_client/v2/model/service_list.py

@@ -32,9 +32,9 @@ def openapi_types(_):
 
     def __init__(self_, data: Union[ServiceListData, UnsetType] = unset, **kwargs):
         """
+        The response body for the service list endpoint.
 
-
-        :param data:
+        :param data: A single data item in the service list response.
         :type data: ServiceListData, optional
         """
         if data is not unset:

src/datadog_api_client/v2/model/service_list_data.py

@@ -44,12 +44,12 @@ def __init__(
         **kwargs,
     ):
         """
+        A single data item in the service list response.
 
-
-        :param attributes:
+        :param attributes: Attributes of a service list entry, containing metadata and a list of service names.
         :type attributes: ServiceListDataAttributes, optional
 
-        :param id:
+        :param id: The unique identifier of the service.
         :type id: str, optional
 
         :param type: Services list resource type.

src/datadog_api_client/v2/model/service_list_data_attributes.py

@@ -43,12 +43,12 @@ def __init__(
         **kwargs,
     ):
         """
+        Attributes of a service list entry, containing metadata and a list of service names.
 
-
-        :param metadata:
+        :param metadata: A list of metadata items associated with the service.
         :type metadata: [ServiceListDataAttributesMetadataItems], optional
 
-        :param services:
+        :param services: A list of service names.
         :type services: [str], optional
         """
         if metadata is not unset:

src/datadog_api_client/v2/model/service_list_data_attributes_metadata_items.py

@@ -28,12 +28,12 @@ def openapi_types(_):
 
     def __init__(self_, is_traced: Union[bool, UnsetType] = unset, is_usm: Union[bool, UnsetType] = unset, **kwargs):
         """
+        An object containing metadata flags for a service, indicating whether it is traced by APM or monitored via Universal Service Monitoring.
 
-
-        :param is_traced:
+        :param is_traced: Indicates whether the service is traced by APM.
         :type is_traced: bool, optional
 
-        :param is_usm:
+        :param is_usm: Indicates whether the service uses Universal Service Monitoring.
         :type is_usm: bool, optional
         """
         if is_traced is not unset:

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