Vox Pupuli Tasks Repositories About
Log in

GitHub puppet-r10k
95
95
27
Setup and configure r10k for use with git based environments in puppet

Metadata Valid
No translation
Correct Puppet Version Range
Supported Puppet version range is %{PUPPET_VERSION_RANGE}
With Puppet Version Range
Puppet version range is present in requirements in metadata.json
With Operatingsystem Support
No translation
Supports Only Current Centos
No translation
Supports Latest Centos
No translation
Supports Only Current Ubuntu
No translation
Supports Latest Ubuntu
No translation
In Modulesync Repo
No translation
In Plumbing
Is in plumbing
Has Secrets
Has a .sync.yml file
Synced
Has a .msync.yml file
Latest Modulesync
No translation
Has Modulesync
Is present in voxpupuli/modulesync_config/managed_modules.yml
Released
Is in modulesync_config and in forge releases.
Reference Dot Md
The repository has a REFERENCE.md. It needs to be generated / puppet-strings documentation is missing.

Open Pull Requests

Added bitbucket webhook support for pull request event

Pull Request (PR) description

Adding bitbucket support for a pull request event type.

This Pull Request (PR) fixes the following issues

Fixes 539

Add generate_types to Mcollective R10K plugin
merge-conflicts

This MR includes the following:

  1. generate_types action to Mcollective R10K plugin
  2. feature to kick off generate_types action from the webhook binary
  3. Fix process fork issue introduced in previous commit 90da3cf
[WIP] Refactor classes postrun_command, prerun_command
backwards-incompatible
merge-conflicts

This pull request will prepare the module for data-in-modules and provide a REFERENCE.md. Unfortunately this module uses a lot of classes and I need to figure out which one are private. Because some variables are named or used badly, this change will be backwards incompatible and end up in a major release.

Add additional curl example for environment prefixes
docs
tests-fail

Pull Request (PR) description

The current documentation for triggering the webhook via curl only specifies an example for non-prefixed environments. With the current data structure format, it's unclear whether the full environment name needs to be specified in the 'ref' parameter. This PR implements clear documentation, noting that the full environment name is required.

This Pull Request (PR) contributes a partial fix for the following issues

422