Skip to content

Add REST API to Refresh / Reload DAG Bundle Without Restart #60616

Open

Description

@aporwal17

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

Activity

  1. shashbha14 commented on Jan 16, 2026

    @shashbha14
    Contributor

    I would like to work on this issue.Please assign this to me.

  2. Prajwal7842 commented on Jan 21, 2026

    @Prajwal7842
    Contributor

    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}

  3. potiuk commented on Feb 14, 2026

    @potiuk
    Member

    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.

  4. added a commit that references this issue on Feb 16, 2026
    74b8789
  5. potiuk commented on Mar 2, 2026

    @potiuk
    Member

    @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.

  6. potiuk commented on Mar 2, 2026

    @potiuk
    Member

    @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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions