chore(spec): add missing descriptions [on-call]

.generator/schemas/v2/openapi.yaml

@@ -15554,6 +15554,7 @@ components:
         tags:
           description: Tags to help categorize or filter the page.
           items:
+            description: A tag for categorizing or filtering the page.
             type: string
           type: array
         target:
@@ -36766,6 +36767,7 @@ components:
       description: Response type for listing notification channels for a user
       properties:
         data:
+          description: Array of notification channel data objects.
           items:
             $ref: '#/components/schemas/NotificationChannelData'
           type: array
@@ -36774,10 +36776,12 @@ components:
       description: Response type for listing notification rules for a user
       properties:
         data:
+          description: Array of notification rule data objects.
           items:
             $ref: '#/components/schemas/OnCallNotificationRuleData'
           type: array
         included:
+          description: Array of related resources included in the response.
           items:
             $ref: '#/components/schemas/OnCallNotificationRulesIncluded'
           type: array
@@ -44821,7 +44825,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 +44855,6 @@ components:
       type: object
       x-pipeline-types:
       - logs
-      - metrics
     ObservabilityPipelineOpentelemetrySourceType:
       default: opentelemetry
       description: The source type. The value should always be `opentelemetry`.
@@ -47130,6 +47133,7 @@ components:
         data:
           $ref: '#/components/schemas/OnCallNotificationRuleData'
         included:
+          description: Array of related resources included in the response.
           items:
             $ref: '#/components/schemas/OnCallNotificationRulesIncluded'
           type: array

src/datadog_api_client/v2/model/list_notification_channels_response.py

@@ -34,7 +34,7 @@ def __init__(self_, data: Union[List[NotificationChannelData], UnsetType] = unse
         """
         Response type for listing notification channels for a user
 
-        :param data:
+        :param data: Array of notification channel data objects.
         :type data: [NotificationChannelData], optional
         """
         if data is not unset:

src/datadog_api_client/v2/model/list_on_call_notification_rules_response.py

@@ -44,10 +44,10 @@ def __init__(
         """
         Response type for listing notification rules for a user
 
-        :param data:
+        :param data: Array of notification rule data objects.
         :type data: [OnCallNotificationRuleData], optional
 
-        :param included:
+        :param included: Array of related resources included in the response.
         :type included: [OnCallNotificationRulesIncluded], optional
         """
         if data is not unset:

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/on_call_notification_rule.py

@@ -47,7 +47,7 @@ def __init__(
         :param data: Data for an on-call notification rule
         :type data: OnCallNotificationRuleData
 
-        :param included:
+        :param included: Array of related resources included in the response.
         :type included: [OnCallNotificationRulesIncluded], optional
         """
         if included 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