Hi all,

As many of you know, airflowctl is on the way for its 1.0.0 release step by
step and has already been stated as a dependency in AIP-94. Building on
that, I have drafted a new Airflow Improvement Proposal: Decouple Remote
Commands from airflow CLI (to airflowctl).

Today, many airflow CLI commands duplicate functionality that already
exists in the Public API/airflowctl. This results in:

   -

   Duplicate development effort (API + CLI both need maintenance),
   -

   Security risks (CLI can directly interact with the metadatabase,
   bypassing RBAC),
   -

   Inconsistent user experience (differences between CLI and API behaviour).

With this AIP, the goal is to:

   -

   Deprecate Remote commands in the airflow CLI,
   -

   Provide equivalent functionality in a dedicated API-driven tool:
   airflowctl,
   -

   Ensure all Remote operations go through the API, strengthening RBAC and
   auditability*.*
   -

   Keep airflow CLI for local administrative commands only (e.g., db shell,
   process management).

This will simplify maintenance, improve security, and give users a clearer
separation between local vs. remote operations.

Full details are in the proposal in Confluence:
https://cwiki.apache.org/confluence/x/XorHFg

I would love to hear your thoughts, feedback, and concerns.

Thanks,
-- 
Bugra Ozturk

Reply via email to