Update: please see https://github.com/elastic/logstash/issues/6393 for the new offline plugin proposal
There are various bugs around the overall offline plugin install/update/uninstall workflow. This meta ticket is to collate and track these issues.
There is some work that has been done before to improve the situation but it did not get merged or reviewed. https://github.com/elastic/logstash/pull/4779
@ph some reviewing was done on #4779 but problems were found.
... also some ideas in #4787
HTTP_PROXY and HTTPS_PROXY aren't correctly used downstream by jar-dependency when it fetches the pom files. see https://github.com/elastic/logstash/issues/6044#issuecomment-253845907
I suggest we update this issue with the new proposed --prepare-offline workflow that will use @ph's mechanism for generating self-contained plugins file that include all dependencies and is offline installable and which should replace the global pack/unpack stuff.
Good idea @colinsurprenant; I've linked the original post directly to the issue with the new proposal.
Closing this issue since #6404 was merged.
I'm not sure you can close this issue yet. At least when I run this on an offline, with both the old pack/unpack, and new prepare offline method, this thing still tries to connect to the internet, and bombs out with
ERROR: Something went wrong when installing XXXXXX, message: Connection reset by peer
I am experiencing this w/ 5.2.
Can you open a new issue including what plugin you are trying to pack and
what command you are using?
On Mon, Feb 6, 2017 at 6:46 PM Jalon notifications@github.com wrote:
I'm not sure you can close this issue yet. At least when I run this on an
offline, with both the old pack/unpack, and new prepare offline method,
this thing still tries to connect to the internet, and bombs out with
ERROR: Something went wrong when installing XXXXXX, message: Connection
reset by peerI am experiencing this w/ 5.2.
—
You are receiving this because you modified the open/close state.Reply to this email directly, view it on GitHub
https://github.com/elastic/logstash/issues/5906#issuecomment-277851884,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAACgESahWX5mYjN8LguzaR9UxoeK0c2ks5rZ7DBgaJpZM4J8PFv
.
Sure thing