fat-catTW opened a new pull request, #72715:
URL: https://github.com/apache/airflow/pull/72715
<!-- SPDX-License-Identifier: Apache-2.0
https://www.apache.org/licenses/LICENSE-2.0 -->
<!--
Thank you for contributing!
Please provide above a brief description of the changes made in this pull
request.
Write a good git commit message following this guide:
https://chris.beams.io/posts/git-commit/
Please make sure that your code changes are covered with tests.
And in case of new features or big changes remember to adjust the
documentation.
For user-facing UI changes, please attach before/after screenshots (or a
short
screen recording) so reviewers can assess the visual impact.
Feel free to ping (in general) for the review if you do not see reaction for
a few days
(72 Hours is the minimum reaction time you can expect from volunteers) - we
sometimes miss notifications.
In case of an existing issue, reference it using one of the following:
* closes: #ISSUE
* related: #ISSUE
-->
## Why
Dag bundle updates currently depend on the periodic refresh interval or
require
restarting Dag processors. This delays the availability of newly deployed
Dags
and makes CI/CD-driven deployments harder to automate.
A refresh request also needs to reach every Dag processor. A single-consumer
queue would allow only one processor to observe the request, leaving other
processors with stale local bundle contents.
closes: #60616
## Solution
Add an asynchronous REST API for requesting a Dag bundle refresh:
`POST /api/v2/dagBundles/{bundle_name}/refresh`
Each request atomically increments a persistent refresh generation stored on
the
bundle. Every Dag processor tracks the latest generation it has processed and
refreshes the bundle when its local generation differs from the persisted
value.
The endpoint returns `202 Accepted` after recording the request. It does not
guarantee that bundle discovery or Dag parsing has completed. Multiple
requests
may be coalesced when a processor observes the latest generation.
Bundle refreshes require Dag edit authorization. Team-owned bundles pass the
owning team scope, while global bundles require global Dag edit access.
The change also updates the database migration, OpenAPI specification,
generated
clients, migration metadata, and API permission documentation.
## Testing
- Added API authorization and response tests.
- Added Dag processor refresh-generation tests.
- Added permission extractor coverage.
- Verified OpenAPI and generated clients.
- Verified database migration checks.
- Ran Ruff and mypy.
- Ran the complete staged-file pre-commit suite.
- Ran focused tests: 172 passed, with 5 PostgreSQL-only tests skipped.
- Ran permission extractor tests: 70 passed.
##### Was generative AI tooling used to co-author this PR?
<!--
If generative AI tooling has been used in the process of authoring this PR,
please
change below checkbox to `[X]` followed by the name of the tool, uncomment
the "Generated-by".
-->
- `[X]` Yes (please specify the tool below)
Generated-by: [Codex] following [the
guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#gen-ai-assisted-contributions)
---
* Read the **[Pull Request
Guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#pull-request-guidelines)**
for more information. Note: commit author/co-author name and email in commits
become permanently public when merged.
* For fundamental code changes, an Airflow Improvement Proposal
([AIP](https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Improvement+Proposals))
is needed.
* When adding dependency, check compliance with the [ASF 3rd Party License
Policy](https://www.apache.org/legal/resolved.html#category-x).
* For significant user-facing changes create newsfragment:
`{pr_number}.significant.rst`, in
[airflow-core/newsfragments](https://github.com/apache/airflow/tree/main/airflow-core/newsfragments).
You can add this file in a follow-up commit after the PR is created so you
know the PR number.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
