Can I access $context in my API? about deprecated-hookshot HOT 5 CLOSED

@davidtheclark you definitely have access to the $context variable since it's currently being used in the request template to pass the HTTP method back to the Lambda function. This should be possible with something like:

'application/json': "{\"headers\":\"$input.params()\",\"ip\":\"$context.identity.sourceIp\",\"method\":\"$context.httpMethod\",\"body\":$input.json('$')}" 

⚠️ You may not notice your new ip property being returned if you perform a simple CloudFormation update. It may require deleting and recreating your stack in order to see your changes until #9 lands.

from deprecated-hookshot.

@emilymdubois: I can do this with my own CloudFormation resources, but if I'm using hookshot to create the API Gateway, I'd need to sneak in and mutate the object that hookshot returned in order to change that line of code, right?

I wonder if a parameter should be added to hookshot allowing the user to specify other things that should show up in the response body JSON.

from deprecated-hookshot.

@emilymdubois do you have an example of how we could change https://github.com/mapbox/hookshot/blob/master/index.js#L175 to expose the entire context object on .passthrough()?

This would be nice to roll up into a breaking version alongside #11

from deprecated-hookshot.

@rclark I haven't experimented with passing the entire $context object back. I only did this with the $input variable, and I think 18a0256 was on the right track.

from deprecated-hookshot.

I think the next thing to investigate is the API Gateway proxy integration, which is designed to be a direct passthrough from an HTTP request to a lambda function.

from deprecated-hookshot.