- 
                Notifications
    You must be signed in to change notification settings 
- Fork 115
Fix indices.put_data_lifecycle API #5583
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 changes against the target branch for the API. 
 You can validate this API yourself by using the  | 
| (It's still failing, but #5563 fixes the other part.) | 
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, good catch!
| Updated the branch to show the success in the automated comment. Thanks for the review, merging! | 
| 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-5583-to-8.19
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 5c8d75f0979890f64184a42c7f59b4b3c50aa2c2
# Push it to GitHub
git push --set-upstream origin backport-5583-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  | 
(cherry picked from commit 5c8d75f)
(cherry picked from commit 5c8d75f)
(cherry picked from commit 5c8d75f) # Conflicts: # output/openapi/elasticsearch-serverless-openapi.json
| 💚 All backports created successfully
 Questions ?Please refer to the Backport tool documentation | 
It looks like there are more issues with
DataStreamLifecycleDownsampling, but let's just focus onindices.put_data_lifecycle. Since it's going to change soon (given elastic/elasticsearch#137023 and #5563), I'd like the existing tests to pass.