Skip to content
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

Support for Proxy Integration for a Proxy Resource #226

Closed
wobeng opened this issue Jan 10, 2017 · 4 comments
Closed

Support for Proxy Integration for a Proxy Resource #226

wobeng opened this issue Jan 10, 2017 · 4 comments
Labels

Comments

@wobeng
Copy link

wobeng commented Jan 10, 2017

Any support for Proxy Integration for a Proxy Resource?

http://docs.aws.amazon.com/apigateway/latest/developerguide/api-gateway-create-api-as-simple-proxy-for-lambda.html

@joevandyk
Copy link

i'd like to know as well.

@jamesls
Copy link
Member

jamesls commented Feb 9, 2017

Could you tell me more about how you'd use this?

I've been looking into making this change, but primarily as an internal refactoring to remove all the VTL mappings I'm using currently. However, switching to proxy integration would mostly be a transparent change for users.

@jamesls
Copy link
Member

jamesls commented Feb 16, 2017

I've implemented this here: #240

One of the nice things about this approach is that you can now return a custom Response instance if you want complete control over the HTTP body/headers/status code

@jamesls
Copy link
Member

jamesls commented Feb 24, 2017

Closing, this is now available to v0.6.0 of chalice.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants