Version information
This version is compatible with:
- Puppet Enterprise 2018.1.x, 2017.3.x, 2017.2.x, 2017.1.x, 2016.4.x
- Puppet >= 4.9.1 < 6.0.0
- Gentoo, , , , , ,
Start using this module
Add this module to your Puppetfile:
mod 'puppet-cron', '1.1.0'
Learn more about managing modules with a PuppetfileDocumentation
Puppet Cron Module
Notes
This module manages cronjobs by placing files in /etc/cron.d
.
rmueller-cron was a detached fork of torrancew/puppet-cron
After v1.0.0, the module was migrated to Vox Pupuli where it is now maintained and released under the puppet namespace.
The current version (starting with v1.0.0) of this module requires Puppet 4.9.1 or greater.
If you are using an older version of Puppet you can pin the version to v0.2.1 which was still compatible with much older Puppet versions.
You can browse the documentation of that version in the v0.2.x branch here.
This module supports configuration of cronjobs via Hiera as well.
For that you need to declare the cron
class.
This module defines the following types:
cron::job
- basic job resourcecron::job::multiple
- basic job resource for multiple jobs per filecron::hourly
- wrapper for hourly jobscron::daily
- wrapper for daily jobscron::weekly
- wrapper for weekly jobscron::monthly
- wrapper for monthly jobs
Installation
As usual use puppet module install puppet-cron
to install it.
Usage
The title of the job (e.g. cron::job { 'title':
) is completely arbitrary. However, there can only be one cron job by that name.
The file in /etc/cron.d/
will be created with the $title
as the file name.
Keep that in mind when choosing the name to avoid overwriting existing system cronjobs and use characters that don't cause problems when used in filenames.
cron
If you want the class to automatically install the correct cron package you can declare the cron
class. By default it will then install the right package.
If you want to use Hiera to configure your cronjobs, you must declare the cron
class.
You can disable the management of the cron package by setting the manage_package
parameter to false
.
You can also specify a different cron package name via package_name
.
By default we try to select the right one for your distribution.
But in some cases (e.g. Gentoo) you might want to overwrite it here.
This class allows specifying the following parameter:
manage_package
- optional - defaults to "true"package_ensure
- optional - defaults to "installed"package_name
- optional - defaults to OS specific default package nameservice_name
- optional - defaults to OS specific default service namemanage_service
- optional - defaults to "true"service_enable
- optional - defaults to "true"service_ensure
- optional - defaults to "running"manage_users_allow
- optional - defaults to false, whether to manage/etc/cron.allow
manage_users_deny
- optional - defaults to false, whether to manage/etc/cron.deny
users_allow
- optional - An array of users to add to/etc/cron.allow
users_deny
- optional - An array of users to add to/etc/cron.deny
Examples:
include cron
or:
class { 'cron':
manage_package => false,
}
cron::job
cron::job
creates generic jobs in /etc/cron.d
.
It allows specifying the following parameters:
ensure
- optional - defaults to "present"command
- required - the command to executeminute
- optional - defaults to "*"hour
- optional - defaults to "*"date
- optional - defaults to "*"month
- optional - defaults to "*"weekday
- optional - defaults to "*"special
- optional - defaults to undefuser
- optional - defaults to "root"environment
- optional - defaults to ""mode
- optional - defaults to "0644"description
- optional - defaults to undef
Example:
This would create the file /etc/cron.d/mysqlbackup
and run the command mysqldump -u root mydb
as root at 2:40 AM every day:
cron::job { 'mysqlbackup':
minute => '40',
hour => '2',
date => '*',
month => '*',
weekday => '*',
user => 'root',
command => 'mysqldump -u root mydb',
environment => [ 'MAILTO=root', 'PATH="/usr/bin:/bin"', ],
description => 'Mysql backup',
}
Hiera example:
---
cron::job:
'mysqlbackup':
command: 'mysqldump -u root mydb'
minute: 0
hour: 0
date: '*'
month: '*'
weekday: '*'
user: root
environment:
- 'MAILTO=root'
- 'PATH="/usr/bin:/bin"'
description: 'Mysql backup'
cron::job::multiple
cron:job::multiple
creates a file in /etc/cron.d
with multiple cron jobs configured in it.
It allows specifying the following parameters:
ensure
- optional - defaults to "present"jobs
- required - an array of hashes of multiple cron jobs using a similar structure ascron::job
-parametersenvironment
- optional - defaults to ""mode
- optional - defaults to "0644"
And the keys of the jobs hash are:
command
- required - the command to executeminute
- optional - defaults to "*"hour
- optional - defaults to "*"date
- optional - defaults to "*"month
- optional - defaults to "*"weekday
- optional - defaults to "*"special
- optional - defaults to undefuser
- optional - defaults to "root"description
- optional - defaults to undef
Example:
cron::job::multiple { 'test_cron_job_multiple':
jobs => [
{
minute => '55',
hour => '5',
date => '*',
month => '*',
weekday => '*',
user => 'rmueller',
command => '/usr/bin/uname',
description => 'print system information',
},
{
command => '/usr/bin/sleep 1',
description => 'Sleeping',
},
{
command => '/usr/bin/sleep 10',
special => 'reboot',
},
],
environment => [ 'PATH="/usr/sbin:/usr/bin:/sbin:/bin"' ],
}
Hiera example:
---
cron::job::multiple:
'test_cron_job_multiple':
jobs:
- {
minute: 55,
hour: 5,
date: '*',
month: '*',
weekday: '*',
user: rmueller,
command: '/usr/bin/uname',
description: 'print system information',
}
- {
command: '/usr/bin/sleep 1',
description: 'Sleeping',
}
- {
command: '/usr/bin/sleep 10',
special: 'reboot',
}
environment:
- 'PATH="/usr/sbin:/usr/bin:/sbin:/bin"'
That will generate the file /etc/cron.d/test_cron_job_multiple
with essentially this content:
PATH="/usr/sbin:/usr/bin:/sbin:/bin"
55 5 * * * rmueller /usr/bin/uname
* * * * * root /usr/bin/sleep 1
@reboot root /usr/bin/sleep 10
cron::hourly
cron::hourly
creates jobs in /etc/cron.d
that run once per hour.
It allows specifying the following parameters:
ensure
- optional - defaults to "present"command
- required - the command to executeminute
- optional - defaults to "0"user
- optional - defaults to "root"environment
- optional - defaults to ""mode
- optional - defaults to "0644"description
- optional - defaults to undef
Example:
This would create the file /etc/cron.d/mysqlbackup_hourly
and run the command mysqldump -u root mydb
as root on the 20th minute of every hour:
cron::hourly { 'mysqlbackup_hourly':
minute => '20',
user => 'root',
command => 'mysqldump -u root mydb',
environment => [ 'MAILTO=root', 'PATH="/usr/bin:/bin"', ],
}
Hiera example:
---
cron::hourly:
'mysqlbackup_hourly':
minute: 20
user: root
command: 'mysqldump -u root mydb'
environment:
- 'MAILTO=root'
- 'PATH="/usr/bin:/bin"'
cron::daily
cron::daily
creates jobs in /etc/cron.d
that run once per day.
It allows specifying the following parameters:
ensure
- optional - defaults to "present"command
- required - the command to executeminute
- optional - defaults to "0"hour
- optional - defaults to "0"user
- optional - defaults to "root"environment
- optional - defaults to ""mode
- optional - defaults to "0644"description
- optional - defaults to undef
Example:
This would create the file /etc/cron.d/mysqlbackup_daily
and run the command mysqldump -u root mydb
as root at 2:40 AM every day, like the above generic example:
cron::daily { 'mysqlbackup_daily':
minute => '40',
hour => '2',
user => 'root',
command => 'mysqldump -u root mydb',
}
Hiera example:
---
cron::daily:
'mysqlbackup_daily':
minute: 40
hour: 2
user: root
command: 'mysqldump -u root mydb'
cron::weekly
cron::weekly
creates jobs in /etc/cron.d
that run once per week.
It allows specifying the following parameters:
ensure
- optional - defaults to "present"command
- required - the command to executeminute
- optional - defaults to "0"hour
- optional - defaults to "0"weekday
- optional - defaults to "0"user
- optional - defaults to "root"environment
- optional - defaults to ""mode
- optional - defaults to "0644"description
- optional - defaults to undef
Example:
This would create the file /etc/cron.d/mysqlbackup_weekly
and run the command mysqldump -u root mydb
as root at 4:40 AM every Sunday, like the above generic example:
cron::weekly { 'mysqlbackup_weekly':
minute => '40',
hour => '4',
weekday => '0',
user => 'root',
command => 'mysqldump -u root mydb',
}
Hiera example:
---
cron::weekly:
'mysqlbackup_weekly':
minute: 40
hour: 4
weekday: 0
user: root
command: 'mysqldump -u root mydb'
cron::monthly
cron::monthly
creates jobs in /etc/cron.d
that run once per month.
It allows specifying the following parameters:
ensure
- optional - defaults to "present"command
- required - the command to executeminute
- optional - defaults to "0"hour
- optional - defaults to "0"date
- optional - defaults to "1"user
- optional - defaults to "root"environment
- optional - defaults to ""mode
- optional - defaults to "0644"description
- optional - defaults to undef
Example:
This would create the file /etc/cron.d/mysqlbackup_monthly
and run the command mysqldump -u root mydb
as root at 3:40 AM the 1st of every month, like the above generic example:
cron::monthly { 'mysqlbackup_monthly':
minute => '40',
hour => '3',
date => '1',
user => 'root',
command => 'mysqldump -u root mydb',
}
Hiera example:
---
cron::monthly:
'mysqlbackup_monthly':
minute: 40
hour: 3
date: 1
user: root
command: 'mysqldump -u root mydb'
Contributors
- Kevin Goess (@kgoess) - Environment variable support + fixes
- Andy Shinn (@andyshinn) - RedHat derivatives package name fix
- Chris Weyl (@RsrchBoy) - Fixed Puppet 3.2 deprecation warnings
- Mathew Archibald (@mattyindustries) - Fixed file ownership issues
- The Community - Continued improvement of this module via bugs and patches
Changelog
All notable changes to this project will be documented in this file. Each new release typically also includes the latest modulesync defaults. These should not affect the functionality of the module.
v1.1.0 (2018-01-19)
Fixed bugs:
- Fix hiera lookup regression #40 (alexjfisher)
Merged pull requests:
- Voxpupuli migration #37 (alexjfisher)
v1.0.0 (2017-10-14)
- BREAKING: Require Puppet version >=4.9.1
- Added type-hinting to all manifest parameters
- Added management of /etc/cron.allow and /etc/cron.deny
- Replaced hiera_hash() with lookup() calls
- Replaced params.pp with in-module data (Hiera 5)
- Replaced create_resources with iterators
- Replaced anchor pattern with contain
- Made the cron::job command attribute optional
v0.2.1 (2017-07-30)
- Added support for special time options
- Rspec fixes
v0.2.0 (2016-11-22)
- BREAKING: Added cron service managment The cron service is now managed by this module and by default the service will be started
- Rspec fixes
v0.1.8 (2016-06-26)
- Added support for Scientific Linux
v0.1.7 (2016-06-12)
- Properly support Gentoo
- Documentation fixes
- Rspec fixes
v0.1.6 (2016-04-10)
- Added description parameters
v0.1.5 (2016-03-06)
- Fix release on forge
v0.1.4 (2016-03-06)
- Added possibility to add jobs from hiera
- Added Debian as supported operating system
- Allow declaration of cron class without managing the cron package
- Properly detect RHEL 5 based cron packages
- Fix puppet-lint warnings
- Add more tests
v0.1.3 (2015-09-20)
- Support for multiple cron jobs in a single file added (cron::job::multiple)
- Make manifest code more readable
- Change header in template to fit standard 80 char wide terminals
- Extend README.md
v0.1.2 (2015-08-13)
- Update to new style of Puppet modules (metadata.json)
v0.1.1 (2015-07-12)
- Make module Puppet 4 compatible
- Fix Travis CI integration
v0.1.0 (2013-08-27)
- Add support for the
ensure
parameter
v0.0.3 (2013-07-04)
- Make job files owned by root
- Fix warnings for Puppet 3.2.2
v0.0.2 (2013-05-11)
- Make mode of job file configurable
v0.0.1 (2013-03-02)
- Initial PuppetForge release
* This Changelog was automatically generated by github_changelog_generator
Copyright 2012-2013 Tray Torrance Apache License Version 2.0, January 2004 http://www.apache.org/licenses/ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION 1. Definitions. "License" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document. "Licensor" shall mean the copyright owner or entity authorized by the copyright owner that is granting the License. "Legal Entity" shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, "control" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity. "You" (or "Your") shall mean an individual or Legal Entity exercising permissions granted by this License. "Source" form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files. "Object" form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types. "Work" shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below). "Derivative Works" shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof. "Contribution" shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, "submitted" means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as "Not a Contribution." "Contributor" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by Licensor and subsequently incorporated within the Work. 2. Grant of Copyright License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form. 3. Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed. 4. Redistribution. You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without modifications, and in Source or Object form, provided that You meet the following conditions: (a) You must give any other recipients of the Work or Derivative Works a copy of this License; and (b) You must cause any modified files to carry prominent notices stating that You changed the files; and (c) You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent, trademark, and attribution notices from the Source form of the Work, excluding those notices that do not pertain to any part of the Derivative Works; and (d) If the Work includes a "NOTICE" text file as part of its distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding those notices that do not pertain to any part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file are for informational purposes only and do not modify the License. You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additional attribution notices cannot be construed as modifying the License. You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative Works as a whole, provided Your use, reproduction, and distribution of the Work otherwise complies with the conditions stated in this License. 5. Submission of Contributions. Unless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions. Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license agreement you may have executed with Licensor regarding such Contributions. 6. Trademarks. This License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor, except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file. 7. Disclaimer of Warranty. Unless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor provides its Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using or redistributing the Work and assume any risks associated with Your exercise of permissions under this License. 8. Limitation of Liability. In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such Contributor has been advised of the possibility of such damages. 9. Accepting Warranty or Additional Liability. While redistributing the Work or Derivative Works thereof, You may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations and/or rights consistent with this License. However, in accepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor by reason of your accepting any such warranty or additional liability. END OF TERMS AND CONDITIONS APPENDIX: How to apply the Apache License to your work. To apply the Apache License to your work, attach the following boilerplate notice, with the fields enclosed by brackets "[]" replaced with your own identifying information. (Don't include the brackets!) The text should be enclosed in the appropriate comment syntax for the file format. We also recommend that a file or class name and description of purpose be included on the same "printed page" as the copyright notice for easier identification within third-party archives. Copyright [yyyy] [name of copyright owner] Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.