Regenerate client from commit e76d911 of spec repo

Author: ci.datadog-api-spec

.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

examples/v2/observability-pipelines/ValidatePipeline_884022323.java

@@ -45,7 +45,7 @@ public ListNotificationChannelsResponse addDataItem(NotificationChannelData data
   }
 
   /**
-   * Getdata
+   * Array of notification channel data objects.
    *
    * @return data
    */

src/main/java/com/datadog/api/client/v2/model/ListNotificationChannelsResponse.java

@@ -51,7 +51,7 @@ public ListOnCallNotificationRulesResponse addDataItem(OnCallNotificationRuleDat
   }
 
   /**
-   * Getdata
+   * Array of notification rule data objects.
    *
    * @return data
    */
@@ -86,7 +86,7 @@ public ListOnCallNotificationRulesResponse addIncludedItem(
   }
 
   /**
-   * Getincluded
+   * Array of related resources included in the response.
    *
    * @return included
    */

src/main/java/com/datadog/api/client/v2/model/ListOnCallNotificationRulesResponse.java

@@ -21,7 +21,7 @@
  * The <code>opentelemetry</code> source receives telemetry data using the OpenTelemetry Protocol
  * (OTLP) over gRPC and HTTP.
  *
- * <p><strong>Supported pipeline types:</strong> logs, metrics
+ * <p><strong>Supported pipeline types:</strong> logs
  */
 @JsonPropertyOrder({
   ObservabilityPipelineOpentelemetrySource.JSON_PROPERTY_GRPC_ADDRESS_KEY,

src/main/java/com/datadog/api/client/v2/model/ObservabilityPipelineOpentelemetrySource.java

@@ -82,7 +82,7 @@ public OnCallNotificationRule addIncludedItem(OnCallNotificationRulesIncluded in
   }
 
   /**
-   * Getincluded
+   * Array of related resources included in the response.
    *
    * @return included
    */

src/main/java/com/datadog/api/client/v2/model/OnCallNotificationRule.java

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