Skip to content
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

[Core deprecations service] Add deprecationType field #96060

Closed
alisonelizabeth opened this issue Apr 1, 2021 · 1 comment · Fixed by #100983
Closed

[Core deprecations service] Add deprecationType field #96060

alisonelizabeth opened this issue Apr 1, 2021 · 1 comment · Fixed by #100983
Labels
enhancement New value added to drive a business result Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc

Comments

@alisonelizabeth
Copy link
Contributor

Currently, the deprecations service (#94845) returns all Kibana deprecations and there is not an easy way to identify between config deprecations and others. I propose adding a deprecationType field (related code) to be able to distinguish between the deprecation types.

Example use case: In Upgrade Assistant, we may want to allow the user to sort by deprecation type. Another option is to show config deprecations in a separate tab, similarly to how the Elasticsearch deprecations are separated by indices and cluster deprecations.

@alisonelizabeth alisonelizabeth added Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc enhancement New value added to drive a business result Feature:Upgrade Assistant labels Apr 1, 2021
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-core (Team:Core)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New value added to drive a business result Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants