GitHub puppet-kibana
Kibana Puppet module by Elastic.

Repo Checks ( 18 of 24 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 Centos
No translation
passed
Supports Latest Centos
No translation
failed
Supports Only Current Redhat
No translation
passed
Supports Latest Redhat
No translation
passed
Supports Only Current Fedora
No translation
passed
Supports Latest Fedora
No translation
failed
Supports Only Current Ubuntu
No translation
passed
Supports Latest Ubuntu
No translation
failed
Supports Only Current Amazon
No translation
passed
Supports Latest Amazon
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.
failed

Open Pull Requests

Allow '.' to appear in package release strings.
tests-fail
merge-conflicts

Packages for RedHat/CentOS commonly have versions like:
1.2.3-4.el7

Here's an example in the wild:
https://cbs.centos.org/koji/buildinfo?buildID=12210
The page contains: "Information for build kibana-4.5.4-2.el7"

...and locally-built packages may follow this pattern, as in the case I
encountered.

Without this change, such package versions fail input validation.

<!--

The following list of checkboxes are the prerequisites for getting your contribution accepted.
Please check them as they are completed.

-->

Pull request acceptance prerequisites:

  • [N/A] Signed the CLA (if not already signed)
  • [x] Rebased/up-to-date with base branch
  • [N/A] Updated CHANGELOG.md with patch notes (if necessary)
  • [N/A] Any relevant docs (README.markdown or inline documentation) updated (if necessary)
  • [N/A] Updated CONTRIBUTORS (if you would like attribution)
  • [ ] Tests pass CI
Open PR in GitHub