-
Notifications
You must be signed in to change notification settings - Fork 8.6k
Remove legacy plugin discovery #71927
Copy link
Copy link
Closed
Labels
Feature:New PlatformReleaseStatusItem of high enough importance that it should be called out in release status meetingsItem of high enough importance that it should be called out in release status meetingsTeam:CorePlatform Core services: plugins, logging, config, saved objects, http, ES client, i18n, etc t//Platform Core services: plugins, logging, config, saved objects, http, ES client, i18n, etc t//release_note:breaking
Metadata
Metadata
Assignees
Labels
Feature:New PlatformReleaseStatusItem of high enough importance that it should be called out in release status meetingsItem of high enough importance that it should be called out in release status meetingsTeam:CorePlatform Core services: plugins, logging, config, saved objects, http, ES client, i18n, etc t//Platform Core services: plugins, logging, config, saved objects, http, ES client, i18n, etc t//release_note:breaking
Type
Fields
Give feedbackNo fields configured for issues without a type.
Related to #56205
Once all 1st party legacy plugins have been removed or migrated, we should disable legacy plugin discovery altogether, even for 3rd party plugins.
When we make this change, we also need to add a note to the "breaking changes" doc for 7.10
Blockers by team
@elastic/stack-monitoring-ui
/api/settingsroute to Kibana platform #76416@elastic/kibana-app-arch
/elasticsearch/_msearchendpoint in Index Pattern Management UI #73993@elastic/kibana-core-ui
/elasticsearch/_msearchendpoint in tutorials #73992@elastic/es-ui
@elastic/logs-metrics-ui
@elastic/kibana-gis
@elastic/kibana-security
@elastic/kibana-platform