[meta] Improve deprecation warnings for plugins without an enabled
config in 8.0.
#114188
Closed
34 of 100 tasks
Labels
Feature:Upgrade Assistant
Meta
Team:Kibana Management
Dev Tools, Index Management, Upgrade Assistant, ILM, Ingest Node Pipelines, and more
Summary
In #89584, we identified the list of plugins which will no longer be disable-able in 8.0. In preparation for the PR with the breaking change, we merged #112602, which added deprecation warnings for all affected plugins.
We decided to do this in one PR to ensure no deprecations were forgotten. However, the result was that these warnings are quite generic as they have not been customized to a specific plugin's users. In the Upgrade Assistant, they will simply say
Configuring "foo.enabled" is deprecated and will be removed in 8.0.
, with instructions toRemove "foo.enabled" from the Kibana config file, CLI flag, or environment variable (in Docker only) before upgrading to 8.0.
Some plugins may have alternative configurations that we could instead point users to, which would create a better upgrade experience. For example, some users may have been depending on the
enabled
configs to hide items from the UI. In these cases, pointing users to Feature Controls, if available for that plugin, might be a good option. Alternatively, some plugins have other config options that could be used instead. e.g.,index_lifecycle_management
has aui.enabled
setting which users might prefer to configure.The purpose of this meta issue is to track the list of affected plugins so that teams can determine whether it is possible to provide their users with a better upgrade experience and link any relevant issues/PRs here.
How to customize your deprecation message
List of affected plugins by team
Instructions: Next to each plugin you own, please link to any PRs/issues related to improving your deprecations, and check the box to indicate you have completed this review for your plugin. If you determine no action is necessary, please check the box anyway to confirm that you have reviewed this.
@elastic/apm-ui
@elastic/enterprise-search-frontend
@elastic/fleet
@elastic/kibana-alerting-services #114190
@elastic/kibana-app
@elastic/kibana-app-services
@elastic/kibana-core
telemetry
will already prevent sending usagetelemetry
telemetry
telemetry
@elastic/kibana-gis
@elastic/kibana-presentation
@elastic/kibana-security
spaces_oss<-- removed in 7.16 via Remove spacesOss plugin #109258security_oss<-- removed in 7.16 via Remove securityOss plugin #113946@elastic/kibana-stack-management
dev_tools(does not supportenabled
in7.x
so no deprecation)es_ui_shared(does not supportenabled
in7.x
so no deprecation)x-pack/grokdebugger(does not supportenabled
in7.x
so no deprecation)xpack.grokdebugger(does not supportenabled
in7.x
so no deprecation)xpack.ingest_pipelines(does not supportenabled
in7.x
so no deprecation)xpack.painless_lab(does not supportenabled
in7.x
so no deprecation)xpack.searchprofiler(does not supportenabled
in7.x
so no deprecation)xpack.watcher(does not supportenabled
in7.x
so no deprecation)@elastic/logs-metrics-ui
@elastic/ml-ui
@elastic/observability-ui
@elastic/security-asset-management
@elastic/security-detections-response
@elastic/security-solution
@elastic/security-threat-hunting
@elastic/stack-monitoring-ui
cc @elastic/kibana-stack-management
The text was updated successfully, but these errors were encountered: