From 1c82e4c005e230f2f5513dbf2f3c7261fc8b09f4 Mon Sep 17 00:00:00 2001
From: "ci.datadog-api-spec" <packages@datadoghq.com>
Date: Tue, 8 Sep 2026 20:43:39 +0000
Subject: [PATCH] Regenerate client from commit b74d458 of spec repo

---
 .generator/schemas/v2/openapi.yaml                       | 5 +++++
 features/v2/observability_pipelines.feature              | 1 +
 .../models/ObservabilityPipelineConfig.ts                | 9 +++++++++
 3 files changed, 15 insertions(+)

diff --git a/.generator/schemas/v2/openapi.yaml b/.generator/schemas/v2/openapi.yaml
index 1a0972d5a21f..ec3ac2f57b76 100644
--- a/.generator/schemas/v2/openapi.yaml
+++ b/.generator/schemas/v2/openapi.yaml
@@ -73676,6 +73676,11 @@ components:
           items:
             $ref: '#/components/schemas/ObservabilityPipelineConfigDestinationItem'
           type: array
+        end_to_end_acknowledgements:
+          description: |-
+            Enables end-to-end event delivery confirmation. Without a disk buffer, sources acknowledge events after delivery to all final destinations; when a disk buffer provides the acknowledgment boundary, they acknowledge after durable persistence.
+            Defaults to `false` when omitted. Requires Observability Pipelines Worker 2.14 or later. All configured sources must support this behavior.
+          type: boolean
         pipeline_type:
           $ref: '#/components/schemas/ObservabilityPipelineConfigPipelineType'
         processor_groups:
diff --git a/features/v2/observability_pipelines.feature b/features/v2/observability_pipelines.feature
index 78729ae2e8b9..4eaf5ec16663 100644
--- a/features/v2/observability_pipelines.feature
+++ b/features/v2/observability_pipelines.feature
@@ -34,6 +34,7 @@ Feature: Observability Pipelines
     And the response "data.attributes.config.sources" has length 1
     And the response "data.attributes.config.processor_groups" has length 1
     And the response "data.attributes.config.destinations" has length 1
+    And the response "data.attributes.config" does not have field "end_to_end_acknowledgements"
 
   @team:DataDog/observability-pipelines
   Scenario: Create a pipeline with dedupe processor with cache returns "OK" response
diff --git a/packages/datadog-api-client-v2/models/ObservabilityPipelineConfig.ts b/packages/datadog-api-client-v2/models/ObservabilityPipelineConfig.ts
index 31fb54ffb712..333f25700d97 100644
--- a/packages/datadog-api-client-v2/models/ObservabilityPipelineConfig.ts
+++ b/packages/datadog-api-client-v2/models/ObservabilityPipelineConfig.ts
@@ -18,6 +18,11 @@ export class ObservabilityPipelineConfig {
    * A list of destination components where processed logs are sent.
    */
   "destinations": Array<ObservabilityPipelineConfigDestinationItem>;
+  /**
+   * Enables end-to-end event delivery confirmation. Without a disk buffer, sources acknowledge events after delivery to all final destinations; when a disk buffer provides the acknowledgment boundary, they acknowledge after durable persistence.
+   * Defaults to `false` when omitted. Requires Observability Pipelines Worker 2.14 or later. All configured sources must support this behavior.
+   */
+  "endToEndAcknowledgements"?: boolean;
   /**
    * The type of data being ingested. Defaults to `logs` if not specified.
    */
@@ -66,6 +71,10 @@ export class ObservabilityPipelineConfig {
       type: "Array<ObservabilityPipelineConfigDestinationItem>",
       required: true,
     },
+    endToEndAcknowledgements: {
+      baseName: "end_to_end_acknowledgements",
+      type: "boolean",
+    },
     pipelineType: {
       baseName: "pipeline_type",
       type: "ObservabilityPipelineConfigPipelineType",