Correct log4j2 syntax in the example #479
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
peternied
added
bug
In the [yml format](https://logging.apache.org/log4j/2.x/manual/configuration.html#Configuration_with_Properties) in of the log4j properties file, a logger is declared with logger.LOGGER_NAME.name, the value of LOGGER_NAME can be set as desired by the user. When the example included the `.` operator it was treated as another object and 'security' was referenced as a key which didn't resolve to anything. Signed-off-by: Peter Nied <[email protected]>
peternied
force-pushed
the
peternied-oidc
branch
from
e8863ed to
a3893f5
Compare
|
FYI @opensearch-project/security |
cliu123
approved these changes
Mar 29, 2022
davidlago
approved these changes
Mar 30, 2022
Naarcha-AWS
approved these changes
Mar 31, 2022
4 tasks
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
In the yml format in of the log4j properties file, a logger is declared with
logger.LOGGER_NAME.name, the value of LOGGER_NAME can be set as desired by the user. When the example included the.operator it was treated as another object and 'security' was referenced as a key which didn't resolve to anything.Issues Resolved
Check List
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.