-
Notifications
You must be signed in to change notification settings - Fork 361
gateway bindings #13
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
Comments
We'd be super happy to accept any auxiliary crate from rust-aws-lambda! I'd also like to explore how we can support how Lambda accepts HTTP requests as a target of an Application Load Balancer. I suspect the interaction would be pretty similar. |
So does this official library not support http events yet? |
No @phillyfan1138, this library only takes care of interacting with the Runtime APIs and start your handler function. To handle API Gateway proxy events or ELB requests you'd need to provide your structs that mirror the event types. Take a look at this crate. We are exploring taking this over in the future (#12) |
I think we may be able to close this now that lambda-http has landed |
Yay, good job @softprops! |
Hi!
It's great to see official lambda support for Rust!
Over at https://github.com/srijs/rust-aws-lambda, we have been building a lambda runtime and various auxiliary crates. We will start to redirect users of the runtime parts over to the official runtime, but similar to #12 I'm keen to hear whether there is interest on your side to move some of the other auxiliary crates.
In particular, there are bindings that translate between the API Gateway proxy events and the types provided by the
http
crate. I'm happy to continue to provide these myself, but I'd like to avoid any duplication of effort, so if you'd like to incorporate these please let me know!The text was updated successfully, but these errors were encountered: