Fix issue with not correctly detecting "warning" log level. #1800
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
dscpinheiro
approved these changes
Sep 2, 2024
dtorok
approved these changes
Sep 2, 2024
dtorok
approved these changes
Sep 3, 2024
philasmar
approved these changes
Sep 3, 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.
Description of changes:
When the log level is set to warning it sets the logging environment variable to
warninstead ofwarningwhich is what the .NET Lambda runtime was using. This PR adds the special case forwarnto translate to .NET'swarningand reworks the integration tests to test the log level through both the legacy .NET environment variable and the Lambda logging configuration properties.By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.