Add end-to-end acknowledgements to Observability Pipelines

.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:

src/datadog_api_client/v2/model/observability_pipeline_config.py

@@ -164,6 +164,7 @@ def openapi_types(_):
 
         return {
             "destinations": ([ObservabilityPipelineConfigDestinationItem],),
+            "end_to_end_acknowledgements": (bool,),
             "pipeline_type": (ObservabilityPipelineConfigPipelineType,),
             "processor_groups": ([ObservabilityPipelineConfigProcessorGroup],),
             "processors": ([ObservabilityPipelineConfigProcessorGroup],),
@@ -173,6 +174,7 @@ def openapi_types(_):
 
     attribute_map = {
         "destinations": "destinations",
+        "end_to_end_acknowledgements": "end_to_end_acknowledgements",
         "pipeline_type": "pipeline_type",
         "processor_groups": "processor_groups",
         "processors": "processors",
@@ -238,6 +240,7 @@ def __init__(
                 ObservabilityPipelineOpentelemetrySource,
             ]
         ],
+        end_to_end_acknowledgements: Union[bool, UnsetType] = unset,
         pipeline_type: Union[ObservabilityPipelineConfigPipelineType, UnsetType] = unset,
         processor_groups: Union[List[ObservabilityPipelineConfigProcessorGroup], UnsetType] = unset,
         processors: Union[List[ObservabilityPipelineConfigProcessorGroup], UnsetType] = unset,
@@ -250,6 +253,10 @@ def __init__(
         :param destinations: A list of destination components where processed logs are sent.
         :type destinations: [ObservabilityPipelineConfigDestinationItem]
 
+        :param end_to_end_acknowledgements: 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 end_to_end_acknowledgements: bool, optional
+
         :param pipeline_type: The type of data being ingested. Defaults to ``logs`` if not specified.
         :type pipeline_type: ObservabilityPipelineConfigPipelineType, optional
 
@@ -271,6 +278,8 @@ def __init__(
             See `Upgrade Your Filter Queries to the New Search Syntax <https://docs.datadoghq.com/observability_pipelines/guide/upgrade_your_filter_queries_to_the_new_search_syntax/>`_ for more information.
         :type use_legacy_search_syntax: bool, optional
         """
+        if end_to_end_acknowledgements is not unset:
+            kwargs["end_to_end_acknowledgements"] = end_to_end_acknowledgements
         if pipeline_type is not unset:
             kwargs["pipeline_type"] = pipeline_type
         if processor_groups is not unset:

tests/v2/features/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