-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
Update the ILM UI to include the ability to wait for snapshot #56776
Comments
Hello @matt-davis-elastic. I think you might have dropped this issue in the wrong repo. The covers the React UI framework (Elastic UI Framework) and doesn't cover the Elasticsearch UI. For those issues, I think you want to make them in Kibana, likely using the Elasticsearch UI label. https://github.com/elastic/kibana/issues?q=is%3Aopen+is%3Aissue+label%3A%22Team%3AElasticsearch+UI%22 |
cc @elastic/es-ui |
@cjcenizal, @matt-davis-elastic and I chatted about this and he is planning on adding some additional detail to this issue when he has a chance. |
For reference, here's the ES PR that introduced the change to the API: elastic/elasticsearch#45067 |
This change adds a "snapshot" action to the delete phase (Snapshot action docs). Here's an example of a policy that uses this action to wait until the
We can surface this in the UI with a single-selection combobox that's populated with the user's SLM policies. A nice enhancement would be a preview that shows up below the combobox that shows you the crucial details of the policy you've selected (and maybe a deep-link into Snapshot Restore). |
Yes, thanks, CJ. Somehow I lost track of this ticket. I think a single-selection combobox would solve this. |
Addressed by #68505 |
ILM is adding a new action in the delete phase that allows ILM to wait for the specified snapshot policy to complete. Can we add something in the UI on the delete phase to allow someone to include the action to wait for a snapshot policy?
@jethr0null let me know if you need any other information.
The text was updated successfully, but these errors were encountered: