-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
remove legacy edge proxy and generic proxy #9581
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
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.
This is incredible, thank you so much for tackling this! I couldn't find the FlaskReponse
in the APIGW code, could you point me to it?
The changes look great, LGTM! 🚀 🧹 I'll let others validate as well, but this is such a great achievement!
2dc3ae8
to
7120a27
Compare
124399e
to
9dd180b
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.
Looks great! 😍
It did really do a great job until now, but still glad we can finally get rid of it 😉
Remaining test failure should be fixed with #9586
7120a27
to
45b80ca
Compare
9dd180b
to
73e6008
Compare
Motivation
#9467 contains the removal of the last legacy providers.
This now allows us to remove the old (and now dead) code around the
GenericProxy
, itsProxyListeners
, and the legacy edge serving.This PR supersedes #9467.
Changes
GenericProxy
, itsProxyListeners
, and the legacy edge serving.flask
andflask-cors
, since those are not used anymore.FlaskResponse
in the API Gateway code. This should be removed asap to finally get rid of the last references.request_context.THREAD_LOCAL
andaccounts.REQUEST_CTX_TLS
. /cc @bentsku @calvernaz @viren-nadkarniTesting