You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
enhancementNew value added to drive a business resultTeam:CoreCore services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc
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.
The text was updated successfully, but these errors were encountered:
enhancementNew value added to drive a business resultTeam:CoreCore services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc
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
andcluster
deprecations.The text was updated successfully, but these errors were encountered: