-
Notifications
You must be signed in to change notification settings - Fork 14.8k
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
AIP-84 Move public api under /api/v2 #47760
AIP-84 Move public api under /api/v2 #47760
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.
Nice, lets rebase and solve conflicts to run the CI
4ec5384
to
545801c
Compare
I think we are missing some occurences in:
|
I am fixing the conflicts and reopening. |
15e32d4
to
d8161ab
Compare
Made the required changes and resolved conflicts. |
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.
CI needs more work I guess, some tests are failing
Working on changing it to /api/v2 and fixing the CI. |
d8161ab
to
ee97839
Compare
@pierrejeambrun Please take a look. |
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 to me, beside comments Ash comments
As mentioned, will create a follow up PR to address the comments by @ashb |
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.
Agree with Ash on generalizing the test paths to eliminate huge updates if needed.
Closes: #47624
^ 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.