fix: default API Gateway integration method #14
Merged
Conversation
This file contains 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
|
Thanks for the clarification and for the fix! v0.7.0 has been just released. |
|
My pleasure! |
|
I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Description
Integration method
ANYis not supported. The reason you can't see it on the AWS Console is because it always defaults toPOST.The has nothing to do with the HTTP method used to call the API and is just how API Gateway calls the Lambda API (the handler will still receive the correct method).
Motivation and Context
Lambda proxy integrations were broken upon first deployment of our services, but worked as soon as they were edited and saved in the console (without making any changes). I investigated and realised that it's because an unsupported integration method was used and upon editing and saving the console automatically changed this to
POST.Breaking Changes
No
How Has This Been Tested?
Currently used in production in the company where I work.