-
Notifications
You must be signed in to change notification settings - Fork 14.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Reorganize api_fastapi
folder into apps
#43062
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good idea, I like the naming as well.
I think we also need to mirror those changes on the test
folder.
In 17_adding_api_endpoints.rst
I think we still have a reference to api_fastapi/views
.
Thanks @pierrejeambrun , I updated docs & tests
|
In preparation for adding apache#43015, this PRs re-organizes the ``api_fastapi``. The goal will be to have 2 apps: `execution_api` (Task Execution API: AIP-72) and the `core_api` (UI and Public APi).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looking good, thanks
In preparation for adding #43015, this PRs re-organizes the
api_fastapi
. The goal will be to have 2 apps:execution_api
(Task Execution API: AIP-72) and thecore_api
(UI and Public API).^ 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 newsfragments.