Skip to content
This repository has been archived by the owner on Apr 12, 2019. It is now read-only.

Store additional plugins in storage #12

Closed
garvincasimir opened this issue Dec 19, 2014 · 2 comments
Closed

Store additional plugins in storage #12

garvincasimir opened this issue Dec 19, 2014 · 2 comments

Comments

@garvincasimir
Copy link
Owner

It would be nice if we moved marvel and any additional plugins to a configurable storage container. The only plugin required by this solution is the discovery plugin so we can make an exception and keep it in the solution. We don't want to be dictating what plugins should be used. We also don't want to make it difficult for people to add their own plugins for their purposes.

@tormodu
Copy link
Contributor

tormodu commented Dec 19, 2014

I can have a look at this.
My proposal is to create a storage container holding x number of plugins. The worker role will download the plugins and copy them to the Elastc Search plugin folder upon initializing,

@garvincasimir
Copy link
Owner Author

Yes, that is exactly what I was thinking. The only thing to keep in mind is the order of tasks. You can download everything at the same time but you must wait till elasticsearch is installed before you can extract the plugins to the plugin folder. The other option is see if elastic search supports multiple plugin folders. If that is the case then you can do everything concurrently.

tormodu pushed a commit to tormodu/Elasticsearch-Azure-PAAS that referenced this issue Jan 7, 2015
tormodu pushed a commit to tormodu/Elasticsearch-Azure-PAAS that referenced this issue Jan 7, 2015
tormodu pushed a commit to tormodu/Elasticsearch-Azure-PAAS that referenced this issue Jan 7, 2015
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants