-
Notifications
You must be signed in to change notification settings - Fork 16.3k
Use HTTP_422_UNPROCESSABLE_CONTENT instead of HTTP_422_UNPROCESSABLE_ENTITY
#58828
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
Looks like we'll need some level of compat here. |
48ac8d9 to
e365c23
Compare
providers/fab/src/airflow/providers/fab/auth_manager/fab_auth_manager.py
Show resolved
Hide resolved
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.
LGTM, just one nit, non blocking
e365c23 to
115b513
Compare
HTTP_422_UNPROCESSABLE_ENTITYis deprecated andHTTP_422_UNPROCESSABLE_CONTENTshould be used instead. That removes quite a few deprecation warnings when the api server starts^ 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 airflow-core/newsfragments.