aporwal17 opened a new issue, #60616:
URL: https://github.com/apache/airflow/issues/60616
### Description
Currently, refreshing a DAG bundle requires a dag processor service restart
or relies on periodic refresh polling interval. This limits automation and
makes it difficult for external systems (CI/CD pipelines, orchestration
platforms, or UI actions) to trigger an immediate DAG refresh after deployment.
This issue proposes adding a REST API endpoint to explicitly refresh or
reload a DAG bundle on demand.
### Use case/motivation
In environments where DAGs are deployed via automated CI/CD pipelines or
managed as versioned bundles, DAG updates are not immediately reflected without
restarting the service or waiting for the next scan interval. This introduces
unnecessary delays and operational overhead.
Providing a REST API to refresh a DAG bundle enables:
- Immediate availability of newly deployed or updated DAGs after a
deployment completes
- Automation-friendly workflows, allowing CI/CD pipelines and external
orchestration systems to trigger DAG refresh programmatically
- Reduced service restarts, minimizing disruption to running workloads
- Improved developer experience, offering a deterministic and observable way
to reload DAG definitions
Overall, this capability supports modern, API-driven operations and makes
DAG lifecycle management more reliable, scalable, and automated.
Introduce a **REST API endpoint** that allows authorized clients to trigger
a DAG bundle refresh.
`POST /api/v2/dag-bundles/{bundle_id}/refresh`
### Related issues
_No response_
### Are you willing to submit a PR?
- [ ] Yes I am willing to submit a PR!
### Code of Conduct
- [x] I agree to follow this project's [Code of
Conduct](https://github.com/apache/airflow/blob/main/CODE_OF_CONDUCT.md)
--
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]
