snapshots clients background added for Azure and S3 #2148
Merged
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
🔍 Preview links for changed docs |
kilfoyle
reviewed
Jul 16, 2025
kilfoyle
approved these changes
Jul 16, 2025
Co-authored-by: David Kilfoyle <41695641+kilfoyle@users.noreply.github.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
This PR adds a paragraph to clarify the meaning of
clientsin the context of the documents for Azure and S3 repositories.We have received feedback for the Azure repository document showing frustration as it wasn't clear what the azure client is and if it's something external to Elastic that the customer needs to take care of.
I've added a short description at the beginning of the docs explaining the context of what the repository client means and how it's configured.
The intro sentence of the S3 repository doc also helps to perceive smoothly why we don't start the procedure by configuring the client, and we directly add a repository.
This should make the reading flow of the docs a bit better.
Closes https://github.com/elastic/docs-feedback/issues/45