Mark cloud-only APIs as private #5235
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
|
Following you can find the validation changes against the target branch for the APIs. No changes detected. You can validate these APIs yourself by using the |
pquentin
changed the title
I'd say no to the backport. |
Anaethelion
approved these changes
Sep 5, 2025
JoshMock
approved these changes
Sep 5, 2025
|
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-5235-to-8.19
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 98ec7ac24c4fbb1acb2abccf8325251ad4a1e4c6
# Push it to GitHub
git push --set-upstream origin backport-5235-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 |
pquentin
added a commit
that referenced
this pull request
Sep 8, 2025
(cherry picked from commit 98ec7ac) # Conflicts: # output/openapi/elasticsearch-openapi.json
💚 All backports created successfully
Questions ?Please refer to the Backport tool documentation |
pquentin
added a commit
that referenced
this pull request
Sep 9, 2025
lcawl
pushed a commit
that referenced
this pull request
Sep 18, 2025
(cherry picked from commit 98ec7ac)
lcawl
pushed a commit
that referenced
this pull request
Sep 18, 2025
(cherry picked from commit 98ec7ac)
💚 All backports created successfully
Questions ?Please refer to the Backport tool documentation |
|
This information was still appearing in the v9 docs, so I created the backports for v9.1 and v9.0 branches. |
pquentin
added a commit
that referenced
this pull request
Sep 19, 2025
(cherry picked from commit 98ec7ac) Co-authored-by: Quentin Pradet <[email protected]>
pquentin
added a commit
that referenced
this pull request
Sep 19, 2025
(cherry picked from commit 98ec7ac) Co-authored-by: Quentin Pradet <[email protected]>
pquentin
added a commit
that referenced
this pull request
Sep 19, 2025
pquentin
added a commit
that referenced
this pull request
Sep 19, 2025
pquentin
added a commit
that referenced
this pull request
Sep 19, 2025
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.
shutdown and autoscaling APIs are private in rest-api-spec, and were never meant to receive public usage. This change means they will disappear from documentation and language clients.
See elastic/elasticsearch#77493 (comment) where it was done in the rest-api-spec. We missed it in the Elasticsearch specification.
I'm not sure about the 8.19 backport.