Skip to content

Research: Explore DAG-bundles as a possibility to offer multiple git repos in one Airflow instance #761

@Maleware

Description

@Maleware

During a meeting we looked at dag bundles as a possible way to achieve multiple git repositories filled with some DAGs and all present in one Airflow instance.

Current known unknowns

(this list can be incomplete)

  1. How do dag-bundles behave if backfill is needed?
  2. They mention limitations in terms of triggering, what is the exact impact of this?
  3. Are their limitations regarding numbers of git repositories or size?
  4. What happens on failure?
  5. How exactly does this fit into release cycles ( Ensure you pull a very specific dag on commit hash or something )
  6. How might cross referencing or cross dependencies look like between dag-bundles? ( if possible at all )

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions