GitHub puppet-logstash
Puppet module to manage Logstash

Repo Checks ( 8 of 25 successfull )
Metadata Valid
No translation
passed
Correct Puppet Version Range
Supported Puppet version range is %{PUPPET_SUPPORT_RANGE}
failed
With Puppet Version Range
Puppet version range is present in requirements in metadata.json
passed
With Operatingsystem Support
No translation
passed
Operatingsystems
No translation
passed
Supports Only Current Redhat
No translation
failed
Supports Latest Redhat
No translation
failed
Supports Only Current Centos
No translation
failed
Supports Latest Centos
No translation
failed
Supports Only Current Oraclelinux
No translation
passed
Supports Latest Oraclelinux
No translation
failed
Supports Only Current Scientific
No translation
passed
Supports Latest Scientific
No translation
failed
Supports Only Current Debian
No translation
failed
Supports Latest Debian
No translation
failed
Supports Only Current Ubuntu
No translation
failed
Supports Latest Ubuntu
No translation
failed
Supports Only Current Opensuse
No translation
passed
Supports Latest Opensuse
No translation
failed
In Modulesync Repo
Is listed as a module managed using modulesync_config
failed
Synced
Has a .msync.yml file
failed
Has Modulesync
Is present in voxpupuli/modulesync_config/managed_modules.yml
failed
Released
Is in modulesync_config and in forge releases.
failed
Valid Sync File
If a (optional) sync file is present, it must not contain a `.travis.yml` entry.
passed
Reference Dot Md
The repository has a REFERENCE.md. It needs to be generated / puppet-strings documentation is missing.
failed

Open Pull Requests

allow overriding default jvm options

move the hardcoded defaults to a module argument to allow adapting them without changing the module.
Uses defaults from current upstream branch (8.5)

Closes gh-397

Open PR in GitHub
Fix modulesync
RFC: WIP: Pipeline configuration improvements
tests-fail
merge-conflicts

This isn't finished. If it looks like I'm going in the right direction (or can be steered that way!), I still have to add docs, examples and tests etc. Hopefully there's enough here for some early feedback. :)

I wanted a way that I could add extra pipelines without having to modify the pipelines parameter passed to the base class each time.

This adds a defined type for adding pipelines and uses concat to write the pipelines.yml file. If you specify a content or source it'll also create the logstash::configfile with the correct path (path.config).

It aims to be backwards compatible. (An array of pipeline configs will still be written to the pipelines.yml as before).

Open PR in GitHub
remove deprecated GC JVM options, fixes #397

Removes the need for the workaround by overwriting deprecated JVM options in https://github.com/voxpupuli/puppet-logstash/issues/397

Open PR in GitHub
logstash: config,patternfile respect `$::logstash::ensure`

otherwise if a server has ensure => false but still calls logstash::configfile for any reason the file will try to be created but fail bc /etc/logstash does not exist

e.g. in your private base.pp you say

include logstash
logstash::configfile {
...
}

but somewhere in hiera you don't want to install logstash on a cluster so you have
logstash::ensure: absent

Open PR in GitHub
modulesync 5.2.0
modulesync
modulesync
Feature file permissions
tests-fail

Use logstashuser and logstashgroup as file owner.
Limit read access for others

Open PR in GitHub
Closes #388
tests-fail

Wrote a wrapper class to call the configfile defined type. Spec tests have also been written for the new functionality. README.md updated with usage examples.

Rspec tests complete successfully and Beaker tests complete successfully on nodesets CentOS 6+7. The Beaker tests do not start to run on the other nodesets with errors such as: "Couldn't find id: {"stream":"Step 1/18 : FROM library/ubuntu:16.04"}"

Open PR in GitHub
Update stdlib module dependency
tests-fail
merge-conflicts
cleanup code
tests-fail
merge-conflicts
Allow puppetlabs/stdlib 6.x and puppet 6.x.
tests-fail
merge-conflicts

Tests appear to be broken.

Open PR in GitHub
Convert module to PDK and cleanup tests
tests-fail
merge-conflicts

I have been using some days now to try to fix all testing issues in the module.
To do this I started out by converting the module to PDK 1.18.1.
I have done my best to map existing setup, but there is some major changes.

I had to skip some acceptance tests in the plugin class for versions >= 6.7 because there have been a change
in the logstash-plugin command.
This command changed in two ways as I can see.
1: it now has to be run from the logstash homedir
2: new option --installed is needed to list only installed plugins

To solve this we either have to drop support for versions < 6.7, or implement a fact that hold the installed logstash version.

Please let me know what you think of my changes..
I really need this module back on track with java 11+ and logstash 7.
Ref #401

Open PR in GitHub