AIP 84: Migrate GET ASSET EVENTS legacy API to fast API #43881
Merged
pierrejeambrun merged 44 commits intoapache:mainfrom Nov 14, 2024
Merged
AIP 84: Migrate GET ASSET EVENTS legacy API to fast API #43881pierrejeambrun merged 44 commits intoapache:mainfrom
pierrejeambrun merged 44 commits intoapache:mainfrom
Conversation
Co-authored-by: Jed Cunningham <[email protected]>
amoghrajesh
reviewed
Nov 13, 2024
Member
pierrejeambrun
left a comment
There was a problem hiding this comment.
A few more comments, overall looking good.
pierrejeambrun
approved these changes
Nov 14, 2024
Member
There was a problem hiding this comment.
Great, thanks!
One last small modification needed following #43932 and we can merge
2 tasks
1 task
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Migrating the connexion API for GET ASSETS EVENTS to fastAPI.
Depends on #43783
related: #43845
Swagger Specs
Response JSON
^ 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.