Repository navigation
Refresh data stream lifecycle update tutorial - #8911
Conversation
Elastic Docs AI PR menuCheck the box to run an AI review for this pull request.
Powered by GitHub Agentic Workflows and docs-actions. For more information, reach out to the docs team. |
Elastic Docs Style Checker (Vale)Summary: 1 suggestion found 💡 Suggestions (1): Optional style improvements. Apply when helpful.
The Vale linter checks documentation changes against the Elastic Docs style guide. To use Vale locally or report issues, refer to Elastic style guide for Vale. |
Replacing the prose review with concrete inline suggestions, at the reviewer's request.
There was a problem hiding this comment.
The writing is clear, LGTM with some inline suggestions.
I checked the rendered previews and tested the API examples on Serverless and Hosted 9.6.0-SNAPSHOT. Retention updates, explain responses, and Hosted lifecycle removal succeeded. The frozen configuration was accepted; actual snapshot conversion and timed deletion were not tested. Older releases and the complete minimally privileged Kibana workflow were not tested live.
Serverless UI testing reproduced the already-linked elastic/kibana#301018: read-only API checks confirmed that indefinite retention saved successfully despite the editor showing the template's seven-day value. Keeping the newer UI removal instructions disabled while elastic/kibana#301013 remains unresolved makes sense.
Separately, the linked Migrate an ILM-managed data stream to data stream lifecycle tutorial could benefit from a shorter opening and more subheadings to break up its long procedures. I opened #9105 to track those improvements separately.
Co-authored-by: Liam Thompson <leemthompo@gmail.com>
Summary
Relates to #7953, elastic/kibana#266070
This PR refreshes https://www.elastic.co/docs/manage-data/lifecycle/data-stream/tutorial-update-existing-data-stream which has been affected by a lot of UI changes in particular in recent releases.
Details
I've made these changes after testing the steps:
Reviewer notes
Per discussion with @SoniaSanzV these docs are affected by the following issues: elastic/kibana#301013, elastic/kibana#301018
Generative AI disclosure
Tool(s) and model(s) used: Grok 4.7