Skip to content
This repository has been archived by the owner on Jun 24, 2022. It is now read-only.

Define a proxy for plugin installation #4

Closed
robin13 opened this issue May 27, 2015 · 4 comments
Closed

Define a proxy for plugin installation #4

robin13 opened this issue May 27, 2015 · 4 comments
Milestone

Comments

@robin13
Copy link
Contributor

robin13 commented May 27, 2015

Ability to define a proxy port like this

@electrical electrical modified the milestone: 0.1.1 Jul 20, 2015
@barryib
Copy link
Contributor

barryib commented Jan 27, 2016

Hello, I have problem with proxy also. I'm going to work on this on our installation, so would like to know what direction to take in order to contribue back to the community.

So what do you think about these proposals:

1- Define proxy for all plugins installation at once

es_plugins_proxy_host: proxy.example.com
es_plugins_proxy_port: 8080

2- Define proxy for particular plugin

es_plugins:
  - plugin: license
  - plugin: marvel-agent
  - plugin: lmenezes/elasticsearch-kopf
    version: master
    proxy_host: proxy.example.com
    proxy_port: 8080

@electrical
Copy link
Contributor

I think it makes sense to have es_proxy_host and es_proxy_port so we can re-use those variables anywhere in the future.
That way its not limited to the plugins.
the proxy_host and proxy_port vars at the es_plugins sections looks good.

@gingerwizard
Copy link

Agreed we should support this +1
Happy to add in next release.

@gingerwizard
Copy link

Closed with pull request 60

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

4 participants