-
Notifications
You must be signed in to change notification settings - Fork 16.4k
Relocate airflow.auth to airflow.api_fastapi.auth #47492
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
Conversation
pierrejeambrun
left a comment
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.
Looks good overall, just one minor adjustment I think.
jscheffl
left a comment
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.
Keep it moving!
|
Just a breeze test to fix |
vincbeck
left a comment
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.
Makes sense
|
Sorry, making a bit of hash of this PR. 🤞🏻 |
|
sdfdsakf;jdsfkldsajfdsjk :table-flip: |
e5b5329 to
d7d1cd4
Compare
All of these pckages are related directly to the API server, so it makes sense to limit the number of "second-level" packages we have under `airflow` package to keep things smaller/more well structured.
This was missed in #47492 as it is explicitly marked as a manual hook to run
This was missed in #47492 as it is explicitly marked as a manual hook to run
This was missed in #47492 as it is explicitly marked as a manual hook to run
This was missed in apache#47492 as it is explicitly marked as a manual hook to run
All of these pckages are related directly to the API server, so it makes sense
to limit the number of "second-level" packages we have under
airflowpackageto keep things smaller/more well structured.
^ 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.rstor{issue_number}.significant.rst, in newsfragments.