Hide c.a.a.p.i.BasicProfileConfigFileLoader noise #56346
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
A recent AWS SDK upgrade has introduced a new source of spurious `WARN` logs when the security manager prevents access to the user's home directory and therefore to their shared client configuration. This is actually the behaviour we want, and it's harmless and handled by the SDK as if the profile config doesn't exist, so this log message is unnecessary noise. This commit suppresses this noisy logging by default. Relates elastic#20313 Closes elastic#56333
DaveCTurner
added
>bug
:Distributed/Discovery-Plugins
|
Pinging @elastic/es-distributed (:Distributed/Discovery-Plugins) |
|
FWIW the bit of SDK code that logs this warning and otherwise handles the exception is |
original-brownbear
approved these changes
May 7, 2020
DaveCTurner
deleted the
2020-05-07-supress-aws-sdk-profile-file-security-warning
branch
DaveCTurner
added a commit
that referenced
this pull request
May 7, 2020
A recent AWS SDK upgrade has introduced a new source of spurious `WARN` logs when the security manager prevents access to the user's home directory and therefore to their shared client configuration. This is actually the behaviour we want, and it's harmless and handled by the SDK as if the profile config doesn't exist, so this log message is unnecessary noise. This commit suppresses this noisy logging by default. Relates #20313 Closes #56333
DaveCTurner
added a commit
that referenced
this pull request
May 7, 2020
A recent AWS SDK upgrade has introduced a new source of spurious `WARN` logs when the security manager prevents access to the user's home directory and therefore to their shared client configuration. This is actually the behaviour we want, and it's harmless and handled by the SDK as if the profile config doesn't exist, so this log message is unnecessary noise. This commit suppresses this noisy logging by default. Relates #20313 Closes #56333
DaveCTurner
added a commit
that referenced
this pull request
May 7, 2020
A recent AWS SDK upgrade has introduced a new source of spurious `WARN` logs when the security manager prevents access to the user's home directory and therefore to their shared client configuration. This is actually the behaviour we want, and it's harmless and handled by the SDK as if the profile config doesn't exist, so this log message is unnecessary noise. This commit suppresses this noisy logging by default. Relates #20313 Closes #56333
DaveCTurner
added a commit
to DaveCTurner/elasticsearch
that referenced
this pull request
Sep 17, 2020
A recent AWS SDK upgrade has introduced a new source of spurious `WARN` logs when the security manager prevents access to the user's home directory and therefore to `$HOME/.aws/config`. This is the behaviour we want, and it's harmless and handled by the SDK as if the config doesn't exist, so this log message is unnecessary noise. This commit suppresses this noisy logging by default. Relates elastic#20313, elastic#56346, elastic#53962 Closes elastic#62493
DaveCTurner
added a commit
that referenced
this pull request
Sep 18, 2020
A recent AWS SDK upgrade has introduced a new source of spurious `WARN` logs when the security manager prevents access to the user's home directory and therefore to `$HOME/.aws/config`. This is the behaviour we want, and it's harmless and handled by the SDK as if the config doesn't exist, so this log message is unnecessary noise. This commit suppresses this noisy logging by default. Relates #20313, #56346, #53962 Closes #62493
DaveCTurner
added a commit
that referenced
this pull request
Sep 18, 2020
A recent AWS SDK upgrade has introduced a new source of spurious `WARN` logs when the security manager prevents access to the user's home directory and therefore to `$HOME/.aws/config`. This is the behaviour we want, and it's harmless and handled by the SDK as if the config doesn't exist, so this log message is unnecessary noise. This commit suppresses this noisy logging by default. Relates #20313, #56346, #53962 Closes #62493
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
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.
A recent AWS SDK upgrade has introduced a new source of spurious
WARNlogswhen the security manager prevents access to the user's home directory and
therefore to their shared client configuration. This is actually the behaviour
we want, and it's harmless and handled by the SDK as if the profile config
doesn't exist, so this log message is unnecessary noise. This commit suppresses
this noisy logging by default.
Relates #20313
Closes #56333