Help: Is there a to (re)create the Lambda event JSON serialization from the Request<Body>? #717
Comments
bassmanitram
changed the title
|
there is not, today. is there a reason you want to directly invoke (with JSON) the second function? can you just call it via its REST frontend? if not, i think your best bet is to not use |
|
It's actually a transitory need - eventually this Rust project will supercede our production Node implementation that enforces certain platform policies by being the first Lambda in an API call - in the case of node business APIs we can wrap the target Node handler. Now, with this, we can wrap Rust business API handlers. But the Node implementation also supports running as a separate Lambda function to invoke Business Lambda functions written for other runtimes. The Rust implementation must progress similarly, except that eventually the central lib will be used to wrap ANY target business Lambda without requiring a second Lambda function - that's the long term goal ... but we want this Rust "proxy" to replace the Node proxy completely ASAP (not least because it runs 200 times faster!), so for a certain time, it must, also, be able to invoke the target business lambda function. That's probably far more than you wanted to know :) Anyway, I solved the problem - https://gist.github.com/bassmanitram/3a22a0b98bfb59b5c5dad4be45888fb8 So we can close this. |
|
The use case is a REST API integration Lambda function that modifies the request before passing onto another a Lambda function - but that second Lambda function can be run with or without the first - i.e. it too is written to accept REST API events.
The text was updated successfully, but these errors were encountered: