Introduce LambdaRuntimeClientProtocol #344
Merged
Conversation
This file contains hidden or 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
fabianfett
reviewed
Aug 28, 2024
fabianfett
approved these changes
Aug 28, 2024
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.
Motivation:
To start implementing the v2 API (#339), we first want to introduce the
LambdaRuntimeClientProtocol. Objects conforming to this protocol can then be used withLambdaRuntime.Modifications:
LambdaRuntimeClientProtocoland the associatedLambdaResponseStreamWriterprotocol.Invocationstruct toInvocationMetadatasince it does not contain the actual invocation event data itself.Invocationstruct which containsInvocationMetadataandByteBuffer.Result:
LambdaRuntimecan be tested more easily through a mock client conforming toLambdaRuntimeClientProtocol.