- Notifications
You must be signed in to change notification settings - Fork 115
[DOCS] Add link for cluster settings #4491
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
| Following you can find the validation results for the APIs you have changed.
You can validate these APIs yourself by using the |
1f6bf42 to 304b073 Compare | Following you can find the validation results for the APIs you have changed.
You can validate these APIs yourself by using the |
| Following you can find the validation results for the APIs you have changed.
You can validate these APIs yourself by using the |
1 similar comment
| Following you can find the validation results for the APIs you have changed.
You can validate these APIs yourself by using the |
| The backport to To backport manually, run these commands in your terminal: # Fetch latest updates from GitHub git fetch # Create a new working tree git worktree add .worktrees/backport-8.19 8.19 # Navigate to the new working tree cd .worktrees/backport-8.19 # Create a new branch git switch --create backport-4491-to-8.19 # Cherry-pick the merged commit of this pull request and resolve the conflicts git cherry-pick -x --mainline 1 93cbe0b3bcd4996a2939c4ffa1dd7553441e32b5 # Push it to GitHub git push --set-upstream origin backport-4491-to-8.19 # Go back to the original working tree cd ../.. # Delete the working tree git worktree remove .worktrees/backport-8.19Then, create a pull request where the |
| The backport to To backport manually, run these commands in your terminal: # Fetch latest updates from GitHub git fetch # Create a new working tree git worktree add .worktrees/backport-8.18 8.18 # Navigate to the new working tree cd .worktrees/backport-8.18 # Create a new branch git switch --create backport-4491-to-8.18 # Cherry-pick the merged commit of this pull request and resolve the conflicts git cherry-pick -x --mainline 1 93cbe0b3bcd4996a2939c4ffa1dd7553441e32b5 # Push it to GitHub git push --set-upstream origin backport-4491-to-8.18 # Go back to the original working tree cd ../.. # Delete the working tree git worktree remove .worktrees/backport-8.18Then, create a pull request where the |
| The backport to To backport manually, run these commands in your terminal: # Fetch latest updates from GitHub git fetch # Create a new working tree git worktree add .worktrees/backport-9.0 9.0 # Navigate to the new working tree cd .worktrees/backport-9.0 # Create a new branch git switch --create backport-4491-to-9.0 # Cherry-pick the merged commit of this pull request and resolve the conflicts git cherry-pick -x --mainline 1 93cbe0b3bcd4996a2939c4ffa1dd7553441e32b5 # Push it to GitHub git push --set-upstream origin backport-4491-to-9.0 # Go back to the original working tree cd ../.. # Delete the working tree git worktree remove .worktrees/backport-9.0Then, create a pull request where the |
(cherry picked from commit 93cbe0b)
💚 All backports created successfully
Questions ?Please refer to the Backport tool documentation |
(cherry picked from commit 93cbe0b)
💚 All backports created successfully
Questions ?Please refer to the Backport tool documentation |
(cherry picked from commit 93cbe0b)
💚 All backports created successfully
Questions ?Please refer to the Backport tool documentation |
Relates to #4435
This PR adds a link from the get and update cluster settings APIs to https://www.elastic.co/docs/deploy-manage/stack-settings since the full list of settings that can be updated is in the narrative docs rather than the API reference docs.