Add logGroupName and logStreamName to LambdaContext (follow up)#664
Merged
Conversation
Read AWS_LAMBDA_LOG_GROUP_NAME and AWS_LAMBDA_LOG_STREAM_NAME environment variables once at runtime initialization and pass them as stored properties through LambdaContext, matching the pattern used by Python, Node.js, and other AWS Lambda runtimes. Closes #662 Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
The proposal document reflects the original design and should not be modified retroactively. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Use String? with nil default instead of empty string, consistent with other optional LambdaContext properties like cognitoIdentity and clientContext. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
3 tasks
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Add to #663