Allow for user-defined client context #110
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Thank for your contribution! Would you be able to add integration tests for this behavior? (on (Make sure that you get the latest code, because the tests have been refactored a little lately) |
|
Thanks @valerena. Rebased and aligned test to latest changes. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Issue #, if available:
Fixes #74 (and enables for aws/aws-sam-cli#1177)
Description of changes:
As explained in the Lambda Invoke documentation, the client context is passed base64-encoded in the
X-Amz-Client-Contextheader.By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.