GitHub puppet-elastic_stack

Repo Checks ( 18 of 22 successfull )
Metadata Valid
No translation
passed
Correct Puppet Version Range
Supported Puppet version range is %{PUPPET_SUPPORT_RANGE}
passed
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 Debian
No translation
passed
Supports Latest Debian
No translation
passed
Supports Only Current Opensuse
No translation
passed
Supports Latest Opensuse
No translation
failed
Supports Only Current Redhat
No translation
passed
Supports Latest Redhat
No translation
passed
Supports Only Current Sles
No translation
passed
Supports Latest Sles
No translation
failed
Supports Only Current Ubuntu
No translation
passed
Supports Latest Ubuntu
No translation
failed
In Modulesync Repo
Is listed as a module managed using modulesync_config
passed
Synced
Has a .msync.yml file
passed
Latest Modulesync
Has been synchronized with the latest tagged version of modulesync_config
failed
Has Modulesync
Is present in voxpupuli/modulesync_config/managed_modules.yml
passed
Released
Is in modulesync_config and in forge releases.
passed
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.
passed

Open Pull Requests

Add forced exec of apt-get update to debian side
tests-fail

Since the apt package doesn't force apt-get update when notified, but instead schedules it for somewhere in the run, this change forces apt-get update after adding the repository.
Without this change you sometimes need to run puppet twice, once to add the source and update (usually at end of puppet run) and again to actually install the packages.

Open PR in GitHub
Add an optional key_source parameter to set up the package repository.

Our internal hosts have no access to the internet, hence no option to download GPG-KEY-elasticsearch. This tiny patch adds the option to specify the download location for the GPG file.

Open PR in GitHub
support full customizable repo url
tests-fail
merge-conflicts

If you are interested I can also add documentation and spec tests. We have the problem, that for some of our customers the repo url format is of the following form, which isn't supported by this module:

https://mirror.example.com/elastic-co/packages/6.x/apt-customername

Open PR in GitHub
Make gpg key location and fingerprint configurable

For a completely internal deployment, downloading the repository key directly
from the internet is not an option. This change makes the $keysource and
$key
id variables configurable so an internal mirror can be used.

Open PR in GitHub
Make architecture configurable
merge-conflicts

This allows to set the apt architecture.

Open PR in GitHub