chore(spec): add missing descriptions [redapl-experiences]

.generator/schemas/v2/openapi.yaml

@@ -7474,6 +7474,7 @@ components:
       description: The request body for deleting multiple rows from a reference table.
       properties:
         data:
+          description: List of row resources to delete from the reference table.
           items:
             $ref: '#/components/schemas/BatchDeleteRowsRequestData'
           maxItems: 200
@@ -7485,6 +7486,7 @@ components:
       description: Row resource containing a single row identifier for deletion.
       properties:
         id:
+          description: The primary key value that uniquely identifies the row to delete.
           example: primary_key_value
           type: string
         type:
@@ -7498,6 +7500,8 @@ components:
         reference table.
       properties:
         data:
+          description: List of row resources to create or update in the reference
+            table.
           items:
             $ref: '#/components/schemas/BatchUpsertRowsRequestData'
           maxItems: 200
@@ -7512,6 +7516,8 @@ components:
         attributes:
           $ref: '#/components/schemas/BatchUpsertRowsRequestDataAttributes'
         id:
+          description: The primary key value that uniquely identifies the row to create
+            or update.
           example: primary_key_value
           type: string
         type:
@@ -16064,6 +16070,7 @@ components:
           - tag_1
           - tag_2
           items:
+            description: A tag associated with the reference table.
             type: string
           type: array
       required:
@@ -16215,6 +16222,7 @@ components:
           example:
           - field_1
           items:
+            description: A field name used as a primary key.
             type: string
           type: array
       required:
@@ -16463,6 +16471,7 @@ components:
           - field_1
           - field_2
           items:
+            description: A column header name from the CSV file.
             type: string
           type: array
         part_count:
@@ -16525,6 +16534,7 @@ components:
           description: The pre-signed URLs for uploading parts. These URLs expire
             after 5 minutes.
           items:
+            description: A pre-signed URL for uploading a single file part.
             type: string
           type: array
       type: object
@@ -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`.
@@ -48910,6 +48919,7 @@ components:
           - tag_1
           - tag_2
           items:
+            description: A tag associated with the reference table.
             type: string
           type: array
       type: object
@@ -49040,6 +49050,7 @@ components:
           example:
           - field_1
           items:
+            description: A field name used as a primary key.
             type: string
           type: array
       required:
@@ -66704,6 +66715,7 @@ components:
           - tag_1
           - tag_2
           items:
+            description: A tag associated with the reference table.
             type: string
           type: array
         updated_at:
@@ -66862,6 +66874,7 @@ components:
           example:
           - field_1
           items:
+            description: A field name used as a primary key.
             type: string
           type: array
       required:

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

@@ -52,7 +52,7 @@ public BatchDeleteRowsRequestArray addDataItem(BatchDeleteRowsRequestData dataIt
   }
 
   /**
-   * Getdata
+   * List of row resources to delete from the reference table.
    *
    * @return data
    */

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

@@ -49,7 +49,7 @@ public BatchDeleteRowsRequestData id(String id) {
   }
 
   /**
-   * Getid
+   * The primary key value that uniquely identifies the row to delete.
    *
    * @return id
    */

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

@@ -52,7 +52,7 @@ public BatchUpsertRowsRequestArray addDataItem(BatchUpsertRowsRequestData dataIt
   }
 
   /**
-   * Getdata
+   * List of row resources to create or update in the reference table.
    *
    * @return data
    */

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

@@ -75,7 +75,7 @@ public BatchUpsertRowsRequestData id(String id) {
   }
 
   /**
-   * Getid
+   * The primary key value that uniquely identifies the row to create or update.
    *
    * @return id
    */

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