chore(spec): add missing descriptions [k9-investigation]

.generator/schemas/v2/openapi.yaml

@@ -9898,6 +9898,7 @@ components:
       - data
       type: object
     CaseManagementProjectData:
+      description: Data object representing a case management project.
       properties:
         id:
           description: Unique identifier of the case management project.
@@ -14698,6 +14699,7 @@ components:
       description: List of requests to create cases for security findings.
       properties:
         data:
+          description: Array of case creation request data objects.
           items:
             $ref: '#/components/schemas/CreateCaseRequestData'
           type: array
@@ -15251,6 +15253,7 @@ components:
       description: List of requests to create Jira issues for security findings.
       properties:
         data:
+          description: Array of Jira issue creation request data objects.
           items:
             $ref: '#/components/schemas/CreateJiraIssueRequestData'
           type: array
@@ -25031,6 +25034,7 @@ components:
       description: List of case responses.
       properties:
         data:
+          description: Array of case response data objects.
           items:
             $ref: '#/components/schemas/FindingCaseResponseData'
           type: array
@@ -25067,8 +25071,11 @@ components:
         attributes:
           additionalProperties:
             items:
+              description: A custom attribute value string.
               type: string
             type: array
+          description: Custom attributes associated with the case as key-value pairs
+            where values are string arrays.
           type: object
         closed_at:
           description: Timestamp of when the case was closed.
@@ -25148,6 +25155,7 @@ components:
           description: Project in which the case was created.
       type: object
     FindingData:
+      description: Data object representing a security finding.
       properties:
         id:
           description: Unique identifier of the security finding.
@@ -25374,6 +25382,7 @@ components:
       description: A list of security findings.
       properties:
         data:
+          description: Array of security finding data objects.
           items:
             $ref: '#/components/schemas/FindingData'
           type: array
@@ -44821,7 +44830,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 +44860,6 @@ components:
       type: object
       x-pipeline-types:
       - logs
-      - metrics
     ObservabilityPipelineOpentelemetrySourceType:
       default: opentelemetry
       description: The source type. The value should always be `opentelemetry`.

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

@@ -42,7 +42,7 @@ public CaseManagementProject data(CaseManagementProjectData data) {
   }
 
   /**
-   * Getdata
+   * Data object representing a case management project.
    *
    * @return data
    */

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

@@ -17,7 +17,7 @@
 import java.util.Map;
 import java.util.Objects;
 
-/** */
+/** Data object representing a case management project. */
 @JsonPropertyOrder({
   CaseManagementProjectData.JSON_PROPERTY_ID,
   CaseManagementProjectData.JSON_PROPERTY_TYPE

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

@@ -51,7 +51,7 @@ public CreateCaseRequestArray addDataItem(CreateCaseRequestData dataItem) {
   }
 
   /**
-   * Getdata
+   * Array of case creation request data objects.
    *
    * @return data
    */

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

@@ -52,7 +52,7 @@ public CreateJiraIssueRequestArray addDataItem(CreateJiraIssueRequestData dataIt
   }
 
   /**
-   * Getdata
+   * Array of Jira issue creation request data objects.
    *
    * @return data
    */

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

@@ -52,7 +52,7 @@ public FindingCaseResponseArray addDataItem(FindingCaseResponseData dataItem) {
   }
 
   /**
-   * Getdata
+   * Array of case response data objects.
    *
    * @return data
    */

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

@@ -156,7 +156,7 @@ public FindingCaseResponseDataAttributes putAttributesItem(
   }
 
   /**
-   * Getattributes
+   * Custom attributes associated with the case as key-value pairs where values are string arrays.
    *
    * @return attributes
    */

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

@@ -17,7 +17,7 @@
 import java.util.Map;
 import java.util.Objects;
 
-/** */
+/** Data object representing a security finding. */
 @JsonPropertyOrder({FindingData.JSON_PROPERTY_ID, FindingData.JSON_PROPERTY_TYPE})
 @jakarta.annotation.Generated(
     value = "https://github.com/DataDog/datadog-api-client-java/blob/master/.generator")

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

@@ -45,7 +45,7 @@ public Findings addDataItem(FindingData dataItem) {
   }
 
   /**
-   * Getdata
+   * Array of security finding data objects.
    *
    * @return data
    */

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