chore(spec): add missing descriptions [aws-integrations]

.generator/schemas/v2/openapi.yaml

@@ -2402,6 +2402,7 @@ components:
           - amplify:ListBackendEnvironments
           - amplify:ListBranches
           items:
+            description: An AWS IAM permission required for the Datadog integration.
             example: account:GetContactInformation
             type: string
           type: array
@@ -2461,6 +2462,7 @@ components:
           description: List of Datadog Lambda Log Forwarder ARNs in your AWS account.
             Defaults to `[]`.
           items:
+            description: The ARN of a Datadog Lambda Log Forwarder function.
             example: arn:aws:lambda:us-east-1:123456789012:function:DatadogLambdaLogForwarder
             type: string
           type: array
@@ -2477,6 +2479,7 @@ components:
 
             endpoint.'
           items:
+            description: An AWS service ID for which automatic log collection is enabled.
             example: s3
             type: string
           type: array
@@ -2547,6 +2550,7 @@ components:
           example:
           - s3
           items:
+            description: The name of an AWS service that can send logs to Datadog.
             example: s3
             type: string
           type: array
@@ -2632,6 +2636,7 @@ components:
           - AWS/ElasticMapReduce
           - AWS/Usage
           items:
+            description: An AWS CloudWatch namespace to exclude from metrics collection.
             example: AWS/SQS
             type: string
           type: array
@@ -2646,6 +2651,7 @@ components:
           example:
           - AWS/EC2
           items:
+            description: An AWS CloudWatch namespace to include in metrics collection.
             example: AWS/EC2
             type: string
           type: array
@@ -2700,6 +2706,7 @@ components:
           example:
           - AWS/ApiGateway
           items:
+            description: An AWS CloudWatch namespace name.
             example: AWS/ApiGateway
             type: string
           type: array
@@ -2797,6 +2804,7 @@ components:
           example:
           - us-east-1
           items:
+            description: An AWS region to include in metrics collection.
             example: us-east-1
             type: string
           type: array
@@ -44821,7 +44829,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 +44859,6 @@ components:
       type: object
       x-pipeline-types:
       - logs
-      - metrics
     ObservabilityPipelineOpentelemetrySourceType:
       default: opentelemetry
       description: The source type. The value should always be `opentelemetry`.
@@ -72613,6 +72620,7 @@ components:
           example:
           - AWS/AppSync
           items:
+            description: An AWS X-Ray service name to include in traces collection.
             example: AWS/AppSync
             type: string
           type: array

src/main/java/com/datadog/api/client/v2/model/ObservabilityPipelineOpentelemetrySource.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/test/resources/com/datadog/api/client/v2/api/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