Regenerate client from commit cc7c305 of spec repo

Author: ci.datadog-api-spec

.generator/schemas/v2/openapi.yaml

@@ -8492,6 +8492,7 @@ components:
           - ubuntu-18.04
           - n2.large
           items:
+            description: A label used to select or identify the node.
             type: string
           type: array
         name:
@@ -18972,6 +18973,7 @@ components:
           example:
           - shopist
           items:
+            description: A service name impacted by the incident.
             type: string
           type: array
         severity:
@@ -19139,6 +19141,7 @@ components:
           example:
           - shopist
           items:
+            description: A service name impacted by the incident.
             type: string
           type: array
         severity:
@@ -20957,6 +20960,7 @@ components:
           - resource1
           - resource2
           items:
+            description: A resource name to exclude from faulty deployment detection.
             type: string
           type: array
       type: object
@@ -25416,12 +25420,15 @@ components:
           - '@foo'
           - '@bar'
           items:
+            description: A code owner of the test as inferred from the repository
+              configuration.
             type: string
           type: array
         envs:
           description: List of environments where this test has been flaky.
           example: prod
           items:
+            description: An environment name where this test has been flaky.
             type: string
           type: array
         first_flaked_branch:
@@ -25521,6 +25528,7 @@ components:
           - foo
           - bar
           items:
+            description: A test service name where this test has been flaky.
             type: string
           type: array
         suite:
@@ -36595,8 +36603,10 @@ components:
       x-enum-varnames:
       - LIST_DEPLOYMENT_RULES
     ListDeploymentRulesResponseDataAttributes:
+      description: Attributes of the response for listing deployment rules.
       properties:
         rules:
+          description: The list of deployment rules.
           items:
             $ref: '#/components/schemas/DeploymentRuleResponseDataAttributes'
           type: array
@@ -44821,7 +44831,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 +44861,6 @@ components:
       type: object
       x-pipeline-types:
       - logs
-      - metrics
     ObservabilityPipelineOpentelemetrySourceType:
       default: opentelemetry
       description: The source type. The value should always be `opentelemetry`.

examples/v2/observability-pipelines/ValidatePipeline_884022323.py

@@ -48,7 +48,7 @@ def __init__(
         """
         Data for a list of deployment rules.
 
-        :param attributes:
+        :param attributes: Attributes of the response for listing deployment rules.
         :type attributes: ListDeploymentRulesResponseDataAttributes
 
         :param id: Unique identifier of the deployment rule.

src/datadog_api_client/v2/model/list_deployment_rule_response_data.py

@@ -36,9 +36,9 @@ def openapi_types(_):
 
     def __init__(self_, rules: Union[List[DeploymentRuleResponseDataAttributes], UnsetType] = unset, **kwargs):
         """
+        Attributes of the response for listing deployment rules.
 
-
-        :param rules:
+        :param rules: The list of deployment rules.
         :type rules: [DeploymentRuleResponseDataAttributes], optional
         """
         if rules is not unset:

src/datadog_api_client/v2/model/list_deployment_rules_response_data_attributes.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/observability_pipeline_opentelemetry_source.py

@@ -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