-
Notifications
You must be signed in to change notification settings - Fork 14.3k
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: Migrating GET Dataset events for DAG runs api to fastAPI #43874
AIP-84: Migrating GET Dataset events for DAG runs api to fastAPI #43874
Conversation
Co-authored-by: Jed Cunningham <[email protected]>
Only the last 3 commits are relevant here |
The base branch has been merged, branch needs rebasing. Also you can add the |
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 just a couple of comments.
I'll do a final in depth review when the branch is rebased, it will make the review easier to only have the 'definitive' diff and not also the one from the base branch.
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.
Thanks, a few suggestions
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.
One small suggestion following the change of convention based on Kaxil's PR that was just merged yesterday.
Otherwise looking good and ready to merge.
Thanks
OK i got a green CI. Is this one good to merge @pierrejeambrun? |
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.
Needs rebasing, small need and ready to merge.
Thanks 🎉 |
related #42370
Depends on #43783
Migrating the GET Dataset events for DAG runs to fastAPI
Responses:
Legacy
FastAPI
Swagger spec
^ 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.