Update recovery.asciidoc #114889
Merged
Update recovery.asciidoc #114889
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
The column names where missing from the documentation. I need to investigate the recovery stage. I am not too sure of the values applicable there.
|
Documentation preview: |
|
@redcinelli please enable the option "Allow edits and access to secrets by maintainers" on your PR. For more information, see the documentation. |
elasticsearchmachine
added
v8.15.4
external-contributor
Dug into the recovery types in the code. Added some details
elasticsearchmachine
added
the
needs:triage
redcinelli
added
>docs
|
Pinging @elastic/es-docs (Team:Docs) |
elasticsearchmachine
removed
the
needs:triage
leemthompo
added
auto-backport
|
@redcinelli sorry this got lost in the vortex of GitHub notifications. This LGTM and in the auto-generated API docs that will be the source of truth for 9.0+ looks like they have this info @lcawl wdyt? |
leemthompo
approved these changes
Jan 29, 2025
leemthompo
pushed a commit
to leemthompo/elasticsearch
that referenced
this pull request
Jan 29, 2025
(cherry picked from commit d8874b6)
💚 All backports created successfully
Questions ?Please refer to the Backport tool documentation |
leemthompo
pushed a commit
to leemthompo/elasticsearch
that referenced
this pull request
Jan 29, 2025
(cherry picked from commit d8874b6)
leemthompo
pushed a commit
to leemthompo/elasticsearch
that referenced
this pull request
Jan 29, 2025
(cherry picked from commit d8874b6)
elasticsearchmachine
pushed a commit
that referenced
this pull request
Jan 29, 2025
(cherry picked from commit d8874b6) Co-authored-by: Paulo <[email protected]>
elasticsearchmachine
pushed a commit
that referenced
this pull request
Jan 29, 2025
(cherry picked from commit d8874b6) Co-authored-by: Paulo <[email protected]>
elasticsearchmachine
pushed a commit
that referenced
this pull request
Jan 29, 2025
(cherry picked from commit d8874b6) Co-authored-by: Paulo <[email protected]>
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.
I found the documentation for the
_cat/recoveryapi lacking some information about the available headers.I dug a little into the code base to better understand some part such as which headers are defaults, or what are the possible values for stage.