feat: allow deployment as AWS Lambda#329
Conversation
c6a7c5c to
59ef06e
Compare
Signed-off-by: szubersk <szuberskidamian@gmail.com>
59ef06e to
7e52d2f
Compare
|
Thanks for this PR! Might you be able to make two changes?:
1.) Could you please provide documentation for other users on how to
call the function? They would likely appreciate concrete examples for
common use cases in the README.md.
2.) Perhaps it would be more clear to rename the function to
"aws_lambda_handler".
Thanks again!
|
|
After thinking about this more, I have the following question: why would a new If this new function only makes things slightly easier for end users, then I'd say its not worth the long-term maintenance cost; it would instead need to make things significantly easier to justify the added cost of maintenance and testing. |
|
Since invoking the tool as a new process seems to be the best way to do this in AWS Lambda (both from a user's perspective, as well as from a code maintenance perspective), I suppose I'll close this PR. @szubersk : if you can provide a scenario where it makes sense to use & maintain a wrapper, I'd be eager to hear it! Regardless, I appreciate the effort you've put in! |
No description provided.