Start Kibana with only one plugin (New Platform) #53586
Labels
enhancement
New value added to drive a business result
Feature:New Platform
Team:Core
Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc
I think once we have cut off the old platform and have everything over at (new) Kibana platform, the dependency system, should make it easy to build a command, that we can quickly start Kibana with just one specific plugin. I think that would be very useful for development purposes, since some teams (e.g. APM) currently just trying to manually disable most plugins not needed (but you need to figure that out by yourself).
I'd imagine that we have the following commands to start Kibana just with a specific plugin available (and all the dependencies that plugin requires). I would also by default not start up optional dependencies, but only if required via a specific other parameter.
That would allow for a better stripped down development, without requiring to maintain large disable lists of plugins.
cc @restrry
The text was updated successfully, but these errors were encountered: