-
Notifications
You must be signed in to change notification settings - Fork 201
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
Add support of LambdaFuctionURLRequest/Response #187
base: master
Are you sure you want to change the base?
Add support of LambdaFuctionURLRequest/Response #187
Conversation
Signed-off-by: thomasgouveia <[email protected]>
Signed-off-by: thomasgouveia <[email protected]>
Thanks @thomasgouveia, that's exactly what I was looking for. Would you add an example of how to make use of the AWS Lambda Function URL in deployment please? IE, maybe duplicate sam.yaml and change as |
Oh, the API signature has changed as well, so maybe a sample that makes use the FuctionURL API signature entirely (code + deployment), maybe? Thanks! |
Next time I should check PRs before doing stuff. |
@thomasgouveia I've added your commit to my PR #190 |
If you can help resolve the conflicts I will publish this with the next release |
@sapessi |
Fixes #172
Description of changes:
This PR add the support for AWS Lambda Function URL Request and Response. It was needed to bump the package
aws-lambda-go
to a more recent version.By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
=> I do.