GitHub puppet-cron
Puppet module to manage cron jobs via /etc/cron.d

Repo Checks ( 20 of 26 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 Redhat
No translation
passed
Supports Latest Redhat
No translation
passed
Supports Only Current Centos
No translation
passed
Supports Latest Centos
No translation
failed
Supports Only Current Scientific
No translation
passed
Supports Latest Scientific
No translation
failed
Supports Only Current Debian
No translation
passed
Supports Latest Debian
No translation
passed
Supports Only Current Gentoo
No translation
failed
Supports Latest Gentoo
No translation
failed
Supports Only Current Sles
No translation
passed
Supports Latest Sles
No translation
failed
Supports Only Current Freebsd
No translation
passed
Supports Latest Freebsd
No translation
passed
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

Update job mapping
merge-conflicts
tests-fail

On MR #27 Hiera lookup started using cron::job::XXX which also turned around and used create_resrouces('cron::job::XXX'.

These resources were not in the job directory. I've moved them there. I can only assume that these were lookups were changed due to puppet4's new parameters and having hourly, month, etc were giving warnings as parameters to the cron class.

Open PR in GitHub
modulesync 5.4.0

modulesync 5.4.0

Open PR in GitHub
Support for sensitive environment variables
backwards-incompatible

Pull Request (PR) description

The environment option does not support sensitive value. I would like to put http_proxy=http://user:password@example.com:3128 in an environment variable, but the content is displayed in cleartext in the log.

This PR allow to define an environment content as sensitive as followed:
puppet
cron::job { 'example' :
environment => [
Sensitive('http_proxy=http://user:password@example.com:3128'),
'PATH=/usr/bin',
],
command => 'sleep 10',
}

same for cron::job::multiple

There was validation in the erb template about the environment variables, and funky .join(\n).split(\n) but I think it is no longer necessary. The content is validated by puppet directly on the call to cron::job. Is this behavior a remnant of old puppet when there was no types?

I also removed the environment variable in the cron::job::multiple::jobs array, as it was not defined in the old erb, and kept the same behavior for the epp.

Feel free to raise concern if you think my assumptions were wrong

This Pull Request (PR) fixes the following issues

Open PR in GitHub