-
Notifications
You must be signed in to change notification settings - Fork 137
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
Query params not propagated to lambda from api gateway integration #117
Comments
I think--but I'm not completely sure--that the integration parameters work a little bit differently than you're expecting. I believe that integration parameters are intended to let you remap request parameters. What you need is a
When testing with curl remember to either specify a request for For another example check out: https://github.com/ahl/nojo/blob/master/gordon/settings.yml As a side note, the integration parameter remapping seems at best misleading and at worst useless. |
So, is there no way to use query parameters with APIGateway <-> Lambda via Gordon? |
What I described above is how you use query parameters. |
You have to map your query params to the message body in the message execution section of the apigateway as described here. Below is the exact template im using for my test endpoint.
|
I'm trying to set up an apigateway <-> lambda integration, but am struggling with getting a query param passed to the lambda. From the docs and examples, I see I should have something like the following in my lambda:
Yet, with this, the query string param (
verification_challege
) does not get propagated to the lambda, and events is an empty dict.Am I doing something wrong?
Attached is a sample application to try this: urlparam.zip
After applying,
The text was updated successfully, but these errors were encountered: