Skip to content
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

Use AWS_LAMBDA_LOG_LEVEL env var to set log level for text format #111

Merged
merged 1 commit into from
Aug 29, 2023

Conversation

kotyara1005
Copy link
Contributor

Use AWS_LAMBDA_LOG_LEVEL env var to set log level for text format

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

@kotyara1005
Copy link
Contributor Author

Ping @alex-pewpew @luben

Copy link

@luben luben left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Copy link

@luben luben left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM
So this will not affect in any way the existing functions and will only affect cases where we have AWS_LAMBDA_LOG_LEVEL set and format is not JSON.

awslambdaric/bootstrap.py Show resolved Hide resolved
awslambdaric/lambda_runtime_log_utils.py Show resolved Hide resolved
awslambdaric/lambda_runtime_log_utils.py Show resolved Hide resolved
awslambdaric/bootstrap.py Show resolved Hide resolved
awslambdaric/bootstrap.py Show resolved Hide resolved
tests/test_bootstrap.py Outdated Show resolved Hide resolved
Copy link
Contributor

@alex-pewpew alex-pewpew left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, please squash commits

@briensea briensea merged commit 9efb462 into aws:main Aug 29, 2023
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants