Skip to content

Create airflow.core.* module structure for Server-client separation #51554

Open

Description

@kaxil

Move the current server components under airflow.core.* module structure & namespace to establish clear boundaries for AIP-72 server-client separation to clearly mark server components.

Example:

  • airflow.models.* → airflow.core.models.*
  • airflow.jobs.* → airflow.core.jobs.*
  • airflow.executors.* → airflow.core.executors.*
  • airflow.api_fastapi.* → airflow.core.api.*

Success Criteria

  • All server components in airflow.core.* namespace
  • No internal code imports from old locations
  • All tests pass with new structure
  • Clear separation between server and shared components

Activity

  1. converted this from a draft issue on Jun 9, 2025
  2. rich7420 commented on Nov 13, 2025

    @rich7420
    Contributor

    Hello , Could I try this?

  3. potiuk commented on Nov 13, 2025

    @potiuk
    Member

    Same here - this is more of a "meta-task" rather than task that can be easily accomplished.

  4. rich7420 commented on Nov 13, 2025

    @rich7420
    Contributor

    thanks!

  5. amoghrajesh commented on Jan 5, 2026

    @amoghrajesh
    Contributor

    Self assigning this one, will pick it up soon.

  6. self-assigned this
    on Jan 5, 2026
  7. added this to the Airflow 3.3.0 milestone on Jan 7, 2026
  8. amoghrajesh commented on Feb 4, 2026

    @amoghrajesh
    Contributor

    As discussed on mailing list, this can happen only after client server separation is complete, ie: 3.3+

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

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions