From c02c6c901db1da5b94fcf4ac078c986e011581c4 Mon Sep 17 00:00:00 2001 From: "ci.datadog-api-spec" Date: Tue, 25 Aug 2026 16:02:22 +0000 Subject: [PATCH] Regenerate client from commit 025e17e of spec repo --- .generator/schemas/v2/openapi.yaml | 13 +++++++++++++ .../v2/model/observability_pipeline_config.py | 9 +++++++++ tests/v2/features/observability_pipelines.feature | 4 ++-- 3 files changed, 24 insertions(+), 2 deletions(-) diff --git a/.generator/schemas/v2/openapi.yaml b/.generator/schemas/v2/openapi.yaml index e24a358f1b..34fa211e75 100644 --- a/.generator/schemas/v2/openapi.yaml +++ b/.generator/schemas/v2/openapi.yaml @@ -72239,6 +72239,12 @@ components: items: $ref: "#/components/schemas/ObservabilityPipelineConfigDestinationItem" type: array + end_to_end_acknowledgements: + description: |- + Enables end-to-end event delivery confirmation for the pipeline. When enabled, sources confirm receipt only after all destinations have successfully received the events. + Requires Observability Pipelines Worker 2.14 or later. All configured sources must support this behavior. + example: true + type: boolean pipeline_type: $ref: "#/components/schemas/ObservabilityPipelineConfigPipelineType" processor_groups: @@ -177228,6 +177234,7 @@ paths: inputs: - datadog-agent-source type: datadog_logs + end_to_end_acknowledgements: true sources: - id: datadog-agent-source type: datadog_agent @@ -177267,6 +177274,7 @@ paths: inputs: - my-processor-group type: datadog_logs + end_to_end_acknowledgements: true pipeline_type: logs processor_groups: - enabled: true @@ -177308,6 +177316,7 @@ paths: inputs: - datadog-agent-source type: datadog_logs + end_to_end_acknowledgements: true sources: - id: datadog-agent-source type: datadog_agent @@ -177352,6 +177361,7 @@ paths: inputs: - my-processor-group type: datadog_logs + end_to_end_acknowledgements: true pipeline_type: logs processor_groups: - enabled: true @@ -177468,6 +177478,7 @@ paths: inputs: - datadog-agent-source type: datadog_logs + end_to_end_acknowledgements: true sources: - id: datadog-agent-source type: datadog_agent @@ -177516,6 +177527,7 @@ paths: inputs: - my-processor-group type: datadog_logs + end_to_end_acknowledgements: true pipeline_type: logs processor_groups: - enabled: true @@ -177558,6 +177570,7 @@ paths: inputs: - datadog-agent-source type: datadog_logs + end_to_end_acknowledgements: true sources: - id: datadog-agent-source type: datadog_agent diff --git a/src/datadog_api_client/v2/model/observability_pipeline_config.py b/src/datadog_api_client/v2/model/observability_pipeline_config.py index 1b300b8ae9..b24c56f186 100644 --- a/src/datadog_api_client/v2/model/observability_pipeline_config.py +++ b/src/datadog_api_client/v2/model/observability_pipeline_config.py @@ -161,6 +161,7 @@ def openapi_types(_): return { "destinations": ([ObservabilityPipelineConfigDestinationItem],), + "end_to_end_acknowledgements": (bool,), "pipeline_type": (ObservabilityPipelineConfigPipelineType,), "processor_groups": ([ObservabilityPipelineConfigProcessorGroup],), "processors": ([ObservabilityPipelineConfigProcessorGroup],), @@ -170,6 +171,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", @@ -234,6 +236,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, @@ -246,6 +249,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 for the pipeline. When enabled, sources confirm receipt only after all destinations have successfully received the events. + 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 @@ -267,6 +274,8 @@ def __init__( See `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: diff --git a/tests/v2/features/observability_pipelines.feature b/tests/v2/features/observability_pipelines.feature index 8aa6ef3615..17b15b8fc0 100644 --- a/tests/v2/features/observability_pipelines.feature +++ b/tests/v2/features/observability_pipelines.feature @@ -18,7 +18,7 @@ Feature: Observability Pipelines @generated @skip @team:DataDog/observability-pipelines Scenario: Create a new pipeline returns "Conflict" response Given new "CreatePipeline" request - And body with value {"data": {"attributes": {"config": {"destinations": [{"id": "datadog-logs-destination", "inputs": ["my-processor-group"], "type": "datadog_logs"}], "pipeline_type": "logs", "processor_groups": [{"enabled": true, "id": "my-processor-group", "include": "service:my-service", "inputs": ["datadog-agent-source"], "processors": [{"enabled": true, "id": "filter-processor", "include": "status:error", "type": "filter"}, {"enabled": true, "field": "message", "id": "json-processor", "include": "*", "type": "parse_json"}]}], "processors": [], "sources": [{"id": "datadog-agent-source", "type": "datadog_agent"}]}, "name": "Main Observability Pipeline"}, "type": "pipelines"}} + And body with value {"data": {"attributes": {"config": {"destinations": [{"id": "datadog-logs-destination", "inputs": ["my-processor-group"], "type": "datadog_logs"}], "end_to_end_acknowledgements": true, "pipeline_type": "logs", "processor_groups": [{"enabled": true, "id": "my-processor-group", "include": "service:my-service", "inputs": ["datadog-agent-source"], "processors": [{"enabled": true, "id": "filter-processor", "include": "status:error", "type": "filter"}, {"enabled": true, "field": "message", "id": "json-processor", "include": "*", "type": "parse_json"}]}], "processors": [], "sources": [{"id": "datadog-agent-source", "type": "datadog_agent"}]}, "name": "Main Observability Pipeline"}, "type": "pipelines"}} When the request is sent Then the response status is 409 Conflict @@ -121,7 +121,7 @@ Feature: Observability Pipelines Scenario: Update a pipeline returns "Conflict" response Given new "UpdatePipeline" request And request contains "pipeline_id" parameter from "REPLACE.ME" - And body with value {"data": {"attributes": {"config": {"destinations": [{"id": "datadog-logs-destination", "inputs": ["my-processor-group"], "type": "datadog_logs"}], "pipeline_type": "logs", "processor_groups": [{"enabled": true, "id": "my-processor-group", "include": "service:my-service", "inputs": ["datadog-agent-source"], "processors": [{"enabled": true, "id": "filter-processor", "include": "status:error", "type": "filter"}, {"enabled": true, "field": "message", "id": "json-processor", "include": "*", "type": "parse_json"}]}], "processors": [], "sources": [{"id": "datadog-agent-source", "type": "datadog_agent"}]}, "name": "Main Observability Pipeline"}, "id": "3fa85f64-5717-4562-b3fc-2c963f66afa6", "type": "pipelines"}} + And body with value {"data": {"attributes": {"config": {"destinations": [{"id": "datadog-logs-destination", "inputs": ["my-processor-group"], "type": "datadog_logs"}], "end_to_end_acknowledgements": true, "pipeline_type": "logs", "processor_groups": [{"enabled": true, "id": "my-processor-group", "include": "service:my-service", "inputs": ["datadog-agent-source"], "processors": [{"enabled": true, "id": "filter-processor", "include": "status:error", "type": "filter"}, {"enabled": true, "field": "message", "id": "json-processor", "include": "*", "type": "parse_json"}]}], "processors": [], "sources": [{"id": "datadog-agent-source", "type": "datadog_agent"}]}, "name": "Main Observability Pipeline"}, "id": "3fa85f64-5717-4562-b3fc-2c963f66afa6", "type": "pipelines"}} When the request is sent Then the response status is 409 Conflict