You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Add REST API to Refresh / Reload DAG Bundle Without Restart #60616
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.
If there is a plan to implemen this, then I would like to work on this. This is something similar to triggering an on_demand serialization which can take dag_id as the input. If the dag_id is already present in DB, we can get additional info like driver path etc.
There is already some support with this API: /api/v2/parseDagFile/{file_token}
This is not meant to discourage your contribution — quite the opposite! You are still very welcome to work on this issue and submit a PR for it. Simply comment that you are working on it and open a PR when ready.
We found that formal assignments were not working well, as they often prevented others from contributing when the assignee was not actively working on the issue.
This is not meant to discourage your contribution — quite the opposite! You are still very welcome to work on this issue and submit a PR for it. Simply comment that you are working on it and open a PR when ready.
We found that formal assignments were not working well, as they often prevented others from contributing when the assignee was not actively working on the issue.
Activity
shashbha14 commentedon Jan 16, 2026
I would like to work on this issue.Please assign this to me.
Prajwal7842 commentedon Jan 21, 2026
If there is a plan to implemen this, then I would like to work on this. This is something similar to triggering an on_demand serialization which can take dag_id as the input. If the dag_id is already present in DB, we can get additional info like driver path etc.
There is already some support with this API: /api/v2/parseDagFile/{file_token}
potiuk commentedon Feb 14, 2026
There is no need to wait for being assigned to work on things -> I assigned both of you now - up to you who will work on it.
Add REST API to refresh DAG bundle without restart
potiuk commentedon Mar 2, 2026
@Prajwal7842 We are unassigning you from this issue as part of our updated assignment policy.
This is not meant to discourage your contribution — quite the opposite! You are still very welcome to work on this issue and submit a PR for it. Simply comment that you are working on it and open a PR when ready.
We found that formal assignments were not working well, as they often prevented others from contributing when the assignee was not actively working on the issue.
potiuk commentedon Mar 2, 2026
@shashbha14 We are unassigning you from this issue as part of our updated assignment policy.
This is not meant to discourage your contribution — quite the opposite! You are still very welcome to work on this issue and submit a PR for it. Simply comment that you are working on it and open a PR when ready.
We found that formal assignments were not working well, as they often prevented others from contributing when the assignee was not actively working on the issue.