Document the 409 from XCom create and drop a duplicated condition

[ColtenOuO]

Sumarry

Two small fixes to POST /api/v2/dags/{dag_id}/dagRuns/{dag_run_id}/taskInstances/{task_id}/xcomEntries.

The 409 was undocumented. The handler returns 409 Conflict when an XCom with
that key already exists for the task instance, but create_openapi_http_exception_doc
only declared 400 and 404. Clients generated from the spec therefore had no
model for a status the endpoint really does return. Same class of fix as #67570
and #67571.

A duplicated condition. The Dag-run check was nested inside an identical copy of
itself:

ifnotdag_run:
ifnotdag_run:
raiseHTTPException(status.HTTP_404_NOT_FOUND, ...)

Dead code, no behaviour change.

v2-rest-api-generated.yaml and ui/openapi-gen/ are regenerated from the changed
responses= declaration.

[github-actions]

Backport successfully created: v3-3-test

Note: As of Merging PRs targeted for Airflow 3.X
the committer who merges the PR is responsible for backporting the PRs that are bug fixes (generally speaking) to the maintenance branches.

In matter of doubt please ask in #release-management Slack channel.

Status	Branch	Result
✅	v3-3-test

[ColtenOuO]

Sumarry

Two small fixes to POST /api/v2/dags/{dag_id}/dagRuns/{dag_run_id}/taskInstances/{task_id}/xcomEntries.

The 409 was undocumented. The handler returns 409 Conflict when an XCom with
that key already exists for the task instance, but create_openapi_http_exception_doc
only declared 400 and 404. Clients generated from the spec therefore had no
model for a status the endpoint really does return. Same class of fix as #67570
and #67571.

A duplicated condition. The Dag-run check was nested inside an identical copy of
itself:

ifnotdag_run:
ifnotdag_run:
raiseHTTPException(status.HTTP_404_NOT_FOUND, ...)

Dead code, no behaviour change.

v2-rest-api-generated.yaml and ui/openapi-gen/ are regenerated from the changed
responses= declaration.

[github-actions]

Backport successfully created: v3-3-test

Note: As of Merging PRs targeted for Airflow 3.X
the committer who merges the PR is responsible for backporting the PRs that are bug fixes (generally speaking) to the maintenance branches.

In matter of doubt please ask in #release-management Slack channel.

Status	Branch	Result
✅	v3-3-test

[ColtenOuO]

Sumarry

Two small fixes to POST /api/v2/dags/{dag_id}/dagRuns/{dag_run_id}/taskInstances/{task_id}/xcomEntries.

The 409 was undocumented. The handler returns 409 Conflict when an XCom with
that key already exists for the task instance, but create_openapi_http_exception_doc
only declared 400 and 404. Clients generated from the spec therefore had no
model for a status the endpoint really does return. Same class of fix as #67570
and #67571.

A duplicated condition. The Dag-run check was nested inside an identical copy of
itself:

ifnotdag_run:
ifnotdag_run:
raiseHTTPException(status.HTTP_404_NOT_FOUND, ...)

Dead code, no behaviour change.

v2-rest-api-generated.yaml and ui/openapi-gen/ are regenerated from the changed
responses= declaration.

[github-actions]

Backport successfully created: v3-3-test

Note: As of Merging PRs targeted for Airflow 3.X
the committer who merges the PR is responsible for backporting the PRs that are bug fixes (generally speaking) to the maintenance branches.

In matter of doubt please ask in #release-management Slack channel.

Status	Branch	Result
✅	v3-3-test

[ColtenOuO]

Sumarry

Two small fixes to POST /api/v2/dags/{dag_id}/dagRuns/{dag_run_id}/taskInstances/{task_id}/xcomEntries.

The 409 was undocumented. The handler returns 409 Conflict when an XCom with
that key already exists for the task instance, but create_openapi_http_exception_doc
only declared 400 and 404. Clients generated from the spec therefore had no
model for a status the endpoint really does return. Same class of fix as #67570
and #67571.

A duplicated condition. The Dag-run check was nested inside an identical copy of
itself:

ifnotdag_run:
ifnotdag_run:
raiseHTTPException(status.HTTP_404_NOT_FOUND, ...)

Dead code, no behaviour change.

v2-rest-api-generated.yaml and ui/openapi-gen/ are regenerated from the changed
responses= declaration.

[github-actions]

Backport successfully created: v3-3-test

Note: As of Merging PRs targeted for Airflow 3.X
the committer who merges the PR is responsible for backporting the PRs that are bug fixes (generally speaking) to the maintenance branches.

In matter of doubt please ask in #release-management Slack channel.

Status	Branch	Result
✅	v3-3-test

[ColtenOuO]

Sumarry

Two small fixes to POST /api/v2/dags/{dag_id}/dagRuns/{dag_run_id}/taskInstances/{task_id}/xcomEntries.

The 409 was undocumented. The handler returns 409 Conflict when an XCom with
that key already exists for the task instance, but create_openapi_http_exception_doc
only declared 400 and 404. Clients generated from the spec therefore had no
model for a status the endpoint really does return. Same class of fix as #67570
and #67571.

A duplicated condition. The Dag-run check was nested inside an identical copy of
itself:

ifnotdag_run:
ifnotdag_run:
raiseHTTPException(status.HTTP_404_NOT_FOUND, ...)

Dead code, no behaviour change.

v2-rest-api-generated.yaml and ui/openapi-gen/ are regenerated from the changed
responses= declaration.

[github-actions]

Backport successfully created: v3-3-test

Note: As of Merging PRs targeted for Airflow 3.X
the committer who merges the PR is responsible for backporting the PRs that are bug fixes (generally speaking) to the maintenance branches.

In matter of doubt please ask in #release-management Slack channel.

Status	Branch	Result
✅	v3-3-test

[ColtenOuO]

Sumarry

Two small fixes to POST /api/v2/dags/{dag_id}/dagRuns/{dag_run_id}/taskInstances/{task_id}/xcomEntries.

The 409 was undocumented. The handler returns 409 Conflict when an XCom with
that key already exists for the task instance, but create_openapi_http_exception_doc
only declared 400 and 404. Clients generated from the spec therefore had no
model for a status the endpoint really does return. Same class of fix as #67570
and #67571.

A duplicated condition. The Dag-run check was nested inside an identical copy of
itself:

ifnotdag_run:
ifnotdag_run:
raiseHTTPException(status.HTTP_404_NOT_FOUND, ...)

Dead code, no behaviour change.

v2-rest-api-generated.yaml and ui/openapi-gen/ are regenerated from the changed
responses= declaration.

[github-actions]

Backport successfully created: v3-3-test

Note: As of Merging PRs targeted for Airflow 3.X
the committer who merges the PR is responsible for backporting the PRs that are bug fixes (generally speaking) to the maintenance branches.

In matter of doubt please ask in #release-management Slack channel.

Status	Branch	Result
✅	v3-3-test

[ColtenOuO]

Sumarry

Two small fixes to POST /api/v2/dags/{dag_id}/dagRuns/{dag_run_id}/taskInstances/{task_id}/xcomEntries.

The 409 was undocumented. The handler returns 409 Conflict when an XCom with
that key already exists for the task instance, but create_openapi_http_exception_doc
only declared 400 and 404. Clients generated from the spec therefore had no
model for a status the endpoint really does return. Same class of fix as #67570
and #67571.

A duplicated condition. The Dag-run check was nested inside an identical copy of
itself:

ifnotdag_run:
ifnotdag_run:
raiseHTTPException(status.HTTP_404_NOT_FOUND, ...)

Dead code, no behaviour change.

v2-rest-api-generated.yaml and ui/openapi-gen/ are regenerated from the changed
responses= declaration.

[github-actions]

Backport successfully created: v3-3-test

Note: As of Merging PRs targeted for Airflow 3.X
the committer who merges the PR is responsible for backporting the PRs that are bug fixes (generally speaking) to the maintenance branches.

In matter of doubt please ask in #release-management Slack channel.

Status	Branch	Result
✅	v3-3-test

[ColtenOuO]

Sumarry

Two small fixes to POST /api/v2/dags/{dag_id}/dagRuns/{dag_run_id}/taskInstances/{task_id}/xcomEntries.

The 409 was undocumented. The handler returns 409 Conflict when an XCom with
that key already exists for the task instance, but create_openapi_http_exception_doc
only declared 400 and 404. Clients generated from the spec therefore had no
model for a status the endpoint really does return. Same class of fix as #67570
and #67571.

A duplicated condition. The Dag-run check was nested inside an identical copy of
itself:

ifnotdag_run:
ifnotdag_run:
raiseHTTPException(status.HTTP_404_NOT_FOUND, ...)

Dead code, no behaviour change.

v2-rest-api-generated.yaml and ui/openapi-gen/ are regenerated from the changed
responses= declaration.

[github-actions]

Backport successfully created: v3-3-test

Note: As of Merging PRs targeted for Airflow 3.X
the committer who merges the PR is responsible for backporting the PRs that are bug fixes (generally speaking) to the maintenance branches.

In matter of doubt please ask in #release-management Slack channel.

Status	Branch	Result
✅	v3-3-test