-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
APIGW: move current provider in legacy module #11651
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
38fe6ad
to
05f5e80
Compare
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.
Awesome! Really great to see that we're already preparing to sunset the old provider! 😛
From my side this looks great, but:
- I think a change for DMS slipped into this PR.
- It would be great if you could rebase the PR before merging, there was a lot going on in the last few days, and the pipeline was super fragile. I would like to avoid any new issues 😅
541fbcd
to
665baf3
Compare
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.
Superb. I agree with Alex, the removal of so many helpers is great to see!
Thanks for addressing the 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.
Thanks for addressing the comments! Lookin' good! Nice preparation and cleanup!
665baf3
to
11b2164
Compare
Motivation
In order to validate a future switch, making the currently named "NextGen" provider default in the next release, this PR migrates the actually current provider in a
legacy
module in order to clearly separate the "old" and "new" code and help up see what parts of the code currently relies on the old implementation.Changes
legacy
module