-
Notifications
You must be signed in to change notification settings - Fork 24.9k
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
Allow resetting only a subset of feature states #70426
Comments
Pinging @elastic/es-core-infra (Team:Core/Infra) |
@pheyos told me that this is a requirement for the feature reset API to be useful in the ML UI functional tests in Kibana CI. |
With serverless locking down system indices more than stateful Elasticsearch, being able to reset features like ML or transforms without resetting security is becoming more important. Not having this functionality prevents the Appex QA framework tests running against real MKI projects. They have to run against a local dev environment. Would it be possible to schedule this work into the roadmap? Even if it's too late for 8.12, getting this done after that would still be very helpful. |
Thank you for raising this, @droberts195. I created a Jira issue for the Core/Infra team that we'll discuss. Let us come back to you about this. |
In #69469, we added a Reset Feature State API that clears the state of plugins with system indices. It does this by deleting the system indices and performing other necessary cleanup. However, for that initial implementation, the API is all-or-nothing: you can't reset Kibana's state without resetting your security index as well.
We should allow users to reset specific feature states, perhaps by providing an optional list of target features.
The text was updated successfully, but these errors were encountered: