Feature request: Automatically install plugins

[abtpst]

So if i want to install any plugins, i have to run the kibana plugin command. Its a bit cumbersome as i have to install each plugin individually. Can i specify just the names of the plugins somewhere and when kibana starts up, it will automatically install these plugins. I remember that in Kibana 4.1.x, i could add the following to the kibana.yml file

bundled_plugin_ids:
 - plugins/dashboard/index
 - plugins/discover/index
 - plugins/doc/index
 - plugins/kibana/index
 - plugins/markdown_vis/index
 - plugins/metric_vis/index
 - plugins/settings/index
 - plugins/table_vis/index
 - plugins/vis_types/index
 - plugins/visualize/index

is this for already installed plugins? Or is it a way to specify auto install of plugins? Can we do something similar for Kibana 4.4.x?

[spalger]

I like the idea of being able to install multiple plugins with a single call to the command line, and could get behind "auto-installing" plugins.

Just a thought: Installing plugins isn't something that most people will do often, and optimizing the speed of install is probably a waste of time. If you are looking to deploy kibana to many machines, or something like that, I suggest that you:

• install the plugins into a local version of kibana
• archive that install
• deploy that archive build rather than re-installing plugins on every deploy

[Kikketer]

@spalger We have a similar need with multiple plugins. Our build server does the install for us and right now is starting to take longer and longer as each plugin is installed.

Here's the process our build script does:

1. run npm build on Kibana itself
2. untar the result
3. Run the x-pack install via the standard ./bin/kibana-plugin install x-pack
4. Loop over every other custom plugin (4 right now) and does the ./bin/kibana-plugin install on each
5. Re-tar the package

The problem comes when it's actually deployed in a Docker image. The startup spits out a line similar to

Optimizing and caching bundles for graph, monitoring, kibana, timelion, login, logout and status_page. This may take a few minutes

While that is happening, we get an Out of Memory exception and it quits. Then it repeats that over and over as it attempts to start the server back up.

Is this "Optimizing plugins" line normal? I figured it's already optimized by doing all of the installs. Is there some sort of flag that isn't being tripped to signal that it already is optimized?

[spalger]

@Kikketer perhaps the optimize at run time is caused by #10724

[Kikketer]

I checked with the team, we aren't setting the base path. I can go through the official support and send along an example tar.

…

On Fri, Apr 14, 2017 at 12:29 PM Spencer ***@***.***> wrote: @Kikketer <https://github.com/Kikketer> perhaps the optimize at run time is caused by #10724 <#10724> — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#6564 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AA6eWkz1VHOxq7cbEO_o5J60Wk0JwLWcks5rv6zlgaJpZM4Hy-uD> .

[tylersmalley]

This is a really old issue; a lot has changed since it was opened. Primarily, we don't run the optimizer in production, so plugin installation is mostly just copying the files to the plugin directory at this point.