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

Disabling --pluginpath for logstash 1.5 #422

Closed
wants to merge 1 commit into from
Closed

Disabling --pluginpath for logstash 1.5 #422

wants to merge 1 commit into from

Conversation

maoo
Copy link

@maoo maoo commented Jul 23, 2015

Actually it disables it for all versions but 1.4 ... ruby code can be improved, before sending PR

Related to #421

Actually it disables it for all versions but 1.4 ... ruby code can be improved, before sending PR
@davidski
Copy link
Contributor

Careful, 1.5.3 reintroduces the pluginpath option. https://www.elastic.co/blog/logstash-1-5-3-and-1-4-4-released

FYI - the current master, with a few tweaks (reference #418) works for me without any problem with current Logstash releases.

@maoo
Copy link
Author

maoo commented Jul 24, 2015

Thank you @davidski for the pointers, I got Logstash 1.5.3 working using master branch (so I'll close this PR)

Though I still can't install plugins; the following syntax is not working for me:

include_recipe 'logstash::server'
logstash_plugins 'logstash-output-elasticsearch-ec2' do
  instance "server"
  action [:create]
end

The following command doesn't return anything

/opt/logstash/server/bin/plugin list | grep ec2

Though the Chef resource is processed, as I find the following on chef logs:

[2015-07-24T09:38:04+01:00] INFO: Processing logstash_plugins[logstash-output-elasticsearch-ec2] action create (img-logging::logstash line 6)

@maoo maoo closed this Jul 24, 2015
@maoo maoo mentioned this pull request Jul 30, 2015
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants