run lambda_runtime inside Lambda Extensions #411
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
|
The changes seem reasonable to me. @bnusunny have you looked into the Lambda Extension package in this repo? I don't know your use case, but it might help you write that extension. |
|
Yes. I plan to use that package to replace my current implementation once v0.5.0 is released. |
calavera
approved these changes
Feb 9, 2022
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:
#410
Description of changes:
do not panic when "AWS_LAMBDA_LOG_STREAM_NAME" and "AWS_LAMBDA_LOG_GROUP_NAME" are missing. This allows lambda_runtime running inside extensions.
By submitting this pull request