-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
Disable specific plugins at startup #6496
Comments
When apps are implemented as individual plugins, that will be simple to do: console:
enabled: false That said, the settings plugin might be a bit too "core" to exclude, so we might want to build it as a UI in one plugin and a service in another. This way you can simply disable the settings UI without preventing the system from having settings. |
So this is already done right @spalger? We might need another ticket to break out the Kibana tabs into separate plugins but this functionality already exists |
So is @spalger saying that this syntax will already work? I thought he was just proposing the syntax. If it works, great - then yes, we just need a ticket to break out the "core" tabs into separate plugins. |
This totally works. You can even give it a shot straight from the command line: ./bin/kibana --kbn_vislib_vis_types.enabled=false |
Cool, I updated the issue to clarify we're talking about disabling or enabling specific plugins at startup. I'll close this one and create another one. |
@spalger it does not work for me
Dockerfile:
|
Today in Kibana we have 4 separate major tabs: Discover, Visualize, Dashboard, Settings. These are currently implemented as a plugin, but could conceptually be broken out into separate plugins eventually.
In 5.0, we'll be adding more, for instance, Console, and all of installed custom plugins will appear as tabs in the left-hand nav.
It is reasonable for an administrator to want to exclude plugins shipped by default in a specific instance of Kibana at startup (e.g. have an instance that doesn't have access to the Settings or the Console tab).
The text was updated successfully, but these errors were encountered: