-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
APIGW NG fix last tests #11198
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
APIGW NG fix last tests #11198
Conversation
c0f49ae
to
9aa346d
Compare
S3 Image Test Results (AMD64 / ARM64) 2 files 2 suites 3m 31s ⏱️ Results for commit 3597b1d. ♻️ This comment has been updated with latest results. |
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.
🎉 🎈 🎉 All the test! 👀 Congrats!
I only left a comment about the testing configuration function in the helper file 😕, but nothing blocking, this can easily be tackled in a follow up
@@ -110,19 +110,18 @@ def __call__( | |||
headers[f"x-amzn-remapped-{header}"] = value | |||
headers.remove(header) | |||
|
|||
# Those headers are passed through from the response headers, there might be more? | |||
passthrough_headers = ("connection", "content-length") | |||
# # Those headers are passed through from the response headers, there might be more? |
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.
Can probably remove that ;)
# # Those headers are passed through from the response headers, there might be more? | |
# Those headers are passed through from the response headers, there might be more? |
"requestParameters": { | ||
"integration.request.header.Content-Type": "'application/x-www-form-urlencoded'" | ||
}, |
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.
We seem to have a few "testing only" helpers in this file. Should we make a plan to move them to the tests files?
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.
Yes please 😭 We really should, I believe once we migrate the current implementation into a legacy
folder, we can find all imports to legacy
and refactor all of it. This function for example makes no sense and is not even that right...
Ultimately the goal would be to remove this whole file all together and find its usages and refactor it or keep it in the "next-gen" helper file.
3597b1d
to
352ebf2
Compare
LocalStack Community integration with Pro 2 files 2 suites 24m 34s ⏱️ Results for commit 352ebf2. |
Motivation
Fix the last following tests in order to be able to enable a new CI step to test the next gen APIGW invocation logic.
Changes
Testing
Successful run with the flag enabled: https://app.circleci.com/jobs/github/localstack/localstack/227232
TODO
What's left to do: