chef-logstash icon indicating copy to clipboard operation
chef-logstash copied to clipboard

Semi-official Logstash cookbook

Results 38 chef-logstash issues
Sort by recently updated
recently updated
newest added

When using runit if logstash_service gets notified it will always try to enable the service first (creating some templates, etc) because runit's default_action is enable. This change makes it so...

The logstash_instance resource has a misconfiguration which breaks the installation when installing from source. The miscofiguration in in providers/instance.rb line 221 `current: user ls_user` `correct: user ls[:user]` ## LoadError logstash_instance[server]...

This snippet from providers/instance.rb demonstrate the issue: ```ruby @create_account = new_resource.create_account || Logstash.get_attribute_or_default(node, @name, 'create_account') ``` when new_resource.create_account is set to false, `Logstash.get_attribute_or_default(node, @name, 'create_account')` is getting invoked because this...

This commit fixes a bug where boolean properties of the `instance’ resource were getting overriden by default values when they were set to false. Fixes #489 Signed-off-by: Bogdan Katynski

The plugin install executes on every chef run. I assume the guard isn't correct. - execute bin/plugin install logstash-input-s3 * logstash_plugins[logstash-output-loggly] action create (up to date) * execute[bin/plugin install logstash-output-loggly]...

bug

Logrotate file that is generated has invalid path of `*.log` instead of `/opt/logstash//log/*.log` Here is the generated file: ```bash "*.log" { daily create 664 logstash logstash rotate 10 missingok notifempty...

Since the loggly plugin I need is a newer version than the native install plugin, I am trying to use the 2.1.1 version from elasticsearch, however, that is causing ruby...

bug
breaking-change

Right now when chef-client runs it restarts the server every time. This can cause issues with dropped files with things like the S3 Plugin Can the cookbook be changed to...

RE: problems like #481, we should switch all hash keys to strings.

enhancement
breaking-change