-
Notifications
You must be signed in to change notification settings - Fork 115
[DOCS] Add data stream lifecycle links #4490
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 |
|
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 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
|
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-4490-to-8.19
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 180215cbf3999d4148b588fc27e37210b31dedc8
# Push it to GitHub
git push --set-upstream origin backport-4490-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-4490-to-8.18
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 180215cbf3999d4148b588fc27e37210b31dedc8
# Push it to GitHub
git push --set-upstream origin backport-4490-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-4490-to-9.0
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 180215cbf3999d4148b588fc27e37210b31dedc8
# Push it to GitHub
git push --set-upstream origin backport-4490-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 180215c)
💚 All backports created successfully
Questions ?Please refer to the Backport tool documentation |
(cherry picked from commit 180215c)
💚 All backports created successfully
Questions ?Please refer to the Backport tool documentation |
(cherry picked from commit 180215c)
💚 All backports created successfully
Questions ?Please refer to the Backport tool documentation |
This PR adds
@ext_doc_idlinks to https://www.elastic.co/docs/manage-data/lifecycle/data-stream from APIs like get data stream lifecycles, since the Data streams group currently only points to an overview of data streams.This is a demo as part of a discussion with @stefnestor about how to add these types of links in general. The OpenAPI output is generated via make generate and make transform-to-openapi commands.