-
Notifications
You must be signed in to change notification settings - Fork 19
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
Proxy support not working if using the environment #16
Comments
Rubygems test suite for the |
fixed the maven-settings issue. the proxy support from Gem.configuration is still pending - not sure yet how to fix it |
@mkristian This is still an issue today (jar dependencies 0.3.5), I've run into it and I have a setup to reproduce it. Do you want to reopen it or create a new one? I am using a 2 vagrant VM, one with squid3 and the other vm only has access to the squid proxy.
|
@ph will look into this asap |
@mkristian any ETA on when we can expect a new version with #16? Thanks much for the fix. |
@suyograo getting the tests green on the weekend and then I release it and update jruby to bundle the new release |
@mkristian we included 0.3.7 in Logstash 5.1.1, and a user is reporting what looks like a bug in jar_dependencies. See elastic/logstash#6396 for details. |
I cannot test this locally because: * logstash 5.x is not in the official package tree * the local package can be retrieved over VPN * but my local VPN client keeps crashing after a while * SSH proxy works but a Java package `logstash` depends on does not respect HTTP_PROXY "HTTP_PROXY and HTTPS_PROXY environment variables are not correctly respected when jar-dependency fetch the pom" elastic/logstash#6044 (comment) "Proxy support not working if using the environment" mkristian/jar-dependencies#16 mkristian/jar-dependencies#16 (comment)
* s/plugin/logstash-plugin/g `plugin` is deprecated. recent logstash documentation refer to `logstash-plugin`. while here remove `when: ansible_os_family == 'FreeBSD'`. * logstash-plugin is also installed without exec bit * support ubuntu * introduce logstash_package_name because FreeBSD has multiple version of logstash * try logstash 5.x I cannot test this locally because: * logstash 5.x is not in the official package tree * the local package can be retrieved over VPN * but my local VPN client keeps crashing after a while * SSH proxy works but a Java package `logstash` depends on does not respect HTTP_PROXY "HTTP_PROXY and HTTPS_PROXY environment variables are not correctly respected when jar-dependency fetch the pom" elastic/logstash#6044 (comment) "Proxy support not working if using the environment" mkristian/jar-dependencies#16 mkristian/jar-dependencies#16 (comment) * enable DEBUG * more debug flags * mount fdescfs and procfs also, remove DEBUG as it turns out that sysutils/logstash5 has a bug that removes exec bit of bundled gems' binaries. the port has been fixed. * the port has been merged * use canonical port name * s/fdesc/procfs/ * support logstash5 * wait for logstash after starting it in the first ansible play, it restarts logstash immediately after starting. this probably causes a race. * the default port is 9600 * validate logstash configuration files as there are multiple files, you cannot use `validate:`. * a typo * reload logstash instead of restarting it when the change is something in configuration files. * swap single quote and double quote * remove TODOs * pipeline.unsafe_shutdown can be enabled in logstash.yml * visualvm should be handled by its own role * config.reload.automatic can be enabled in logstash.yml * reload handler has been implemented * with ansible-role-redis, you can implement queuing * plugins has been managed by the role * comment why pif file is not used * always run logstash as user logstash as logstash creates directory and files when invoked. if logstash binaries, including logstash-plugin, runs as root, it causes subsequent logstash run to fail. * fix wrong keys * use logstash_config_merged instead of logstash_config * wait for logstash to start in handler there is a race when HUP terminates restart * fix a typo * document the finding * manage jvm.options * add other defaults * document new valiables * add License * add some comments * add comments on the task and the template with new configuration option system, the task and the template will be removed * update the example * add some notices * restore logstash_config no, rc.conf will not be removed as 'conf.d' must bedefined.
I am currently looking to add the proxy support back into logstash 1.5, but I am unable to make the jars download uses a proxy. I was expecting setting the
http_proxy
env variable to an appropriate proxy and the libs management would pick it up.Versions:
Scenarios
Gem.configuration[:proxy]
but in the rubygems test suite they usesGem.configuration[:http_proxy]
. After making my code update both thehttp_proxy
and theproxy
key and adding trace I see that my configuration is correctly send to the mvn class loader (in ruby maven)but the jar download isn't using the proxy.
JARS_MAVEN_SETTINGS
to use it, it doesn't go to the proxy..~/.m2
directory, the jars download will go through the proxySettings.xml
Logstash ref: elastic/logstash#2851
The text was updated successfully, but these errors were encountered: