-
Notifications
You must be signed in to change notification settings - Fork 16.7k
[v3-1-test] Remove dagReports API endpoint (#56609)#56621
[v3-1-test] Remove dagReports API endpoint (#56609)#56621potiuk merged 1 commit intoapache:v3-1-testfrom
dagReports API endpoint (#56609)#56621Conversation
The /api/v2/dagReports endpoint loaded user DAG files directly in the API server process via DagBag, violating Airflow's core architectural principle that the API server must never execute user code.
The endpoint was not used by the UI and had no known consumers. Users needing DAG loading reports should use the airflow dags report CLI command instead, which runs in an isolated process designed to safely execute user code.
(cherry picked from commit 828aaa0)
^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named {pr_number}.significant.rst or {issue_number}.significant.rst, in airflow-core/newsfragments.
API server process via DagBag, violating Airflow's core architectural
principle that the API server must never execute user code.
The endpoint was not used by the UI and had no known consumers. Users
needing DAG loading reports should use the `airflow dags report` CLI
command instead, which runs in an isolated process designed to safely
execute user code.
(cherry picked from commit 828aaa0)
Co-authored-by: Kaxil Naik