Fix up S3 repo logging docs #4301
Open
Conversation
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
✅ Vale Linting ResultsNo issues found on modified lines! |
🔍 Preview links for changed docs |
The docs about verbose logging from the AWS Java SDK only apply to the EOL v1 SDK that we stopped using in 9.1. This commit adjusts the documentation to reflect the new logger names from 9.1 onwards. However, due to elastic/elasticsearch#137556 there was no way to enable this logging at all in 9.1.0-9.1.8 and 9.2.0-9.2.2.
DaveCTurner
force-pushed
the
2025/12/11/repo-s3-logging
branch
from
4bd6582 to
90bef4e
Compare
Contributor
Author
|
I don't like how it renders the tab headers but I'm not sure what to do about that - any advice? 
|
Contributor
Author
|
Yeah ok nested tabs seem slightly nicer to use, still not ideal but better than what I had before 
|
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.
The docs about verbose logging from the AWS Java SDK only apply to the
EOL v1 SDK that we stopped using in 9.1. This commit adjusts the
documentation to reflect the new logger names from 9.1 onwards.
However, due to elastic/elasticsearch#137556 there was no way to enable
this logging at all in 9.1.0-9.1.8 and 9.2.0-9.2.2.