-
Notifications
You must be signed in to change notification settings - Fork 4k
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
feat(appsync): optional operation parameter for lambdaRequest mapping template #15283
Conversation
@asnaseer-resilient would love to know your thoughts! I have a working integration test that I think is pretty comprehensive but wouldn't mind a second glance |
@BryanPan342 Looks perfect - I can't wait for this to be published. Thanks again for doing this 👍 |
Thank you for contributing! Your pull request will be updated from master and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork). |
Thank you for contributing! Your pull request will be updated from master and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork). |
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
… template (aws#15283) **[CORE CHANGES]** Add optional `operation` parameter to `lamdaRequest` mapping template. - Defaults to `"Invoke"` - Allows for `"BatchInvoke"` operations directly through the static `lambdaRequest` function **[MISC]** * Add integration test w/ a verification script to test mapping template * preliminary mapping template unit tests (created an issue to create more testing aws#15274 * Use `path.resolve()` to resolve testing integration test in different directories Fixes: aws#14079 ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
… template (aws#15283) **[CORE CHANGES]** Add optional `operation` parameter to `lamdaRequest` mapping template. - Defaults to `"Invoke"` - Allows for `"BatchInvoke"` operations directly through the static `lambdaRequest` function **[MISC]** * Add integration test w/ a verification script to test mapping template * preliminary mapping template unit tests (created an issue to create more testing aws#15274 * Use `path.resolve()` to resolve testing integration test in different directories Fixes: aws#14079 ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
[CORE CHANGES]
Add optional
operation
parameter tolamdaRequest
mapping template."Invoke"
"BatchInvoke"
operations directly through the staticlambdaRequest
function[MISC]
path.resolve()
to resolve testing integration test in different directoriesFixes: #14079
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license