rsync
Version information
This version is compatible with:
- Puppet Enterprise 2019.8.x, 2019.7.x, 2019.5.x, 2019.4.x, 2019.3.x, 2019.2.x, 2019.1.x, 2019.0.x, 2018.1.x, 2017.3.x, 2017.2.x, 2017.1.x, 2016.5.x, 2016.4.x
- Puppet >= 4.7.0 < 7.0.0
- , , , ,
Start using this module
Add this module to your Puppetfile:
mod 'puppetlabs-rsync', '1.2.0'
Learn more about managing modules with a PuppetfileDocumentation
puppetlabs-rsync
Table of Contents
- Module Description - What does the module do?
- Usage - Configuration options and additional functionality
- Reference - An under-the-hood peek at what the module is doing and how
- Limitations - OS compatibility, etc.
Module description
puppetlabs-rsync manages rsync clients, repositories, and servers as well as providing defines to easily grab data via rsync.
Usage
Install the latest version of rsync
class { 'rsync':
package_ensure => 'latest'
}
Get file 'foo' via rsync
rsync::get { '/foo':
source => "rsync://${rsyncServer}/repo/foo/",
require => File['/foo'],
}
Put file 'foo' on 'rsyncDestHost'
rsync::put { '${rsyncDestHost}:/repo/foo':
user => 'user',
source => "/repo/foo/",
}
Setup default rsync repository
rsync::server::module{ 'repo':
path => $base,
require => File[$base],
}
To disable default values for incoming_chmod
and outgoing_chmod
, and
do not add empty values to the resulting config, set both values to false
rsync::server::module { 'repo':
path => $base,
incoming_chmod => false,
outgoing_chmod => false,
require => File[$base],
}
Configuring via Hiera
rsync::put
, rsync::get
, and rsync::server::module
resources can be
configured using Hiera hashes. For example:
rsync::server::modules:
myrepo:
path: /mypath
incoming_chmod: false
outgoing_chmod: false
myotherrepo:
path: /otherpath
read_only: false
Reference
Classes:
Defined Types:
Classes
rsync
Manage the rsync package.
package_ensure
Ensure the for the rsync package. Any of the valid values for the package resource (present, absent, purged, held, latest) are acceptable.
Default value: 'installed'
manage_package
Setting this to false stops the rsync package resource from being managed.
Default value: true
Defined Types
rsync::get
get files via rsync
source
Required
Source to copy from.
path
Path to copy to.
Default value: $name
user
Username on remote system
purge
If set, rsync will use '--delete'
recursive
If set, rsync will use '-r'
links
If set, rsync will use '--links'
hardlinks
If set, rsync will use '--hard-links'
copylinks
If set, rsync will use '--copy-links'
times
If set, rsync will use '--times'
exclude
String (or array of strings) paths for files to be excluded.
include
String (or array of strings) paths for files to be explicitly included.
exclude_first
If true
, exclude first and then include; the other way around if false
.
Default value: true
keyfile
SSH key used to connect to remote host.
timeout
Timeout in seconds.
Default value: 900
execuser
User to run the command (passed to exec).
options
Default options to pass to rsync (-a).
chown
USER:GROUP simple username/groupname mapping.
chmod
File and/or directory permissions.
logfile
Log file name.
onlyif
Condition to run the rsync command.
rsync::put
put files via rsync
source
Required
Source to copy from.
path
Path to copy to.
Default value: $name
user
Username on target remote system.
purge
If set, rsync will use '--delete'
exclude
String (or array of strings) paths for files to be excluded.
include
String (or array of strings) paths for files to be explicitly included.
exclude_first
If true
, exclude first and then include; the other way around if false
.
Default value: true
keyfile
Path to SSH key used to connect to remote host.
Default value: '/home/${user}/.ssh/id_rsa'
timeout
Timeout in seconds.
Default value: 900
options
Default options to pass to rsync (-a)
rsync::server::module
Sets up a rsync server
path
Required
Path to data.
comment
Rsync comment.
motd
File containing motd info.
pid_file
PID file. Defaults to /var/run/rsyncd.pid. The pid file parameter won't be applied if set to "UNSET"; rsyncd will not use a PID file in this case.
read_only
yes||no
Default value: 'yes'
write_only
yes||no
Default value: 'no'
list
yes||no
Default value: 'no'
uid
uid of rsync server
Default value: 0
gid
gid of rsync server
Default value: 0
incoming_chmod
Incoming file mode
Default value: '644'
outgoing_chmod
Outgoing file mode
Default value: '644'
max_connections
Maximum number of simultaneous connections allowed
Default value: 0
lock_file
File used to support the max connections parameter. Only needed if max_connections > 0.
Default value: '/var/run/rsyncd.lock'
secrets_file
Path to the file that contains the username:password pairs used for authenticating this module.
auth_users
List of usernames that will be allowed to connect to this module (must be undef or an array).
hosts_allow
List of patterns allowed to connect to this module (rsyncd.conf man page for details, must be undef or an array).
hosts_deny
List of patterns allowed to connect to this module (rsyncd.conf man page for details, must be undef or an array).
transfer_logging
Parameter enables per-file logging of downloads and uploads in a format somewhat similar to that used by ftp daemons.
log_format
This parameter allows you to specify the format used for logging file transfers when transfer logging is enabled. See the rsyncd.conf man page for more details.
refuse_options
List of rsync command line options that will be refused by your rsync daemon.
ignore_nonreadable
This tells the rsync daemon to completely ignore files that are not readable by the user.
Parameters:
$source - source to copy from
$path - path to copy to, defaults to $name
$user - username on remote system
$purge - if set, rsync will use '--delete'
$exclude - string (or array) to be excluded
$include - string (or array) to be included
$exclude_first - if 'true' (default) then first exclude and then include; the other way around if 'false'
$keyfile - path to ssh key used to connect to remote host, defaults to /home/${user}/.ssh/id_rsa
$timeout - timeout in seconds, defaults to 900
$options - default options to pass to rsync (-a)
Actions:
put files via rsync
Requires:
$source must be set
Sample Usage:
rsync::put { '${rsyncDestHost}:/repo/foo':
user => 'user',
source => "/repo/foo/",
}
Definition: rsync::server::module
sets up a rsync server
Parameters:
$path - path to data
$comment - rsync comment
$use_chroot - yes||no, defaults to yes
$motd - file containing motd info
$read_only - yes||no, defaults to yes
$write_only - yes||no, defaults to no
$list - yes||no, defaults to no
$uid - uid of rsync server, defaults to 0
$gid - gid of rsync server, defaults to 0
$numeric_ids - don't resolve uids to usernames, defaults to yes
$incoming_chmod - incoming file mode, defaults to 644
$outgoing_chmod - outgoing file mode, defaults to 644
$max_connections - maximum number of simultaneous connections allowed, defaults to 0
$timeout - disconnect client after X seconds of inactivity, defaults to 0
$lock_file - file used to support the max connections parameter, defaults to /var/run/rsyncd.lock only needed if max_connections > 0
$secrets_file - path to the file that contains the username:password pairs used for authenticating this module
$auth_users - list of usernames that will be allowed to connect to this module (must be undef or an array)
$hosts_allow - list of patterns allowed to connect to this module (man 5 rsyncd.conf for details, must be undef or an array)
$hosts_deny - list of patterns allowed to connect to this module (man 5 rsyncd.conf for details, must be undef or an array)
$transfer_logging - parameter enables per-file logging of downloads and uploads in a format somewhat similar to that used by ftp daemons.
$log_file - log messages to the indicated file rather than using syslog
$log_format - This parameter allows you to specify the format used for logging file transfers when transfer logging is enabled. See the rsyncd.conf documentation for more details.
$refuse_options - list of rsync command line options that will be refused by your rsync daemon.
$include - list of files to include
$include_from - file containing a list of files to include
$exclude - list of files to exclude
$exclude_from - file containing a list of files to exclude
$dont_compress - disable compression on matching files
$ignore_nonreadable - This tells the rsync daemon to completely ignore files that are not readable by the user.
Actions:
sets up an rsync server
Requires:
$path must be set
Sample Usage:
# setup default rsync repository
rsync::server::module{ 'repo':
path => $base,
require => File[$base],
}
To disable default values for incoming_chmod
and outgoing_chmod
, and
do not add empty values to the resulting config, set both values to false
rsync::server::module { 'repo':
path => $base,
incoming_chmod => false,
outgoing_chmod => false,
require => File[$base],
}
Configuring via Hiera
rsync::put
, rsync::get
, and rsync::server::module
resources can be
configured using Hiera hashes. For example:
Unsupported Release 1.2.0
Summary
This minor release is a roll up of bug fixes and features
Added
- Add support for CentOS8
pid_file
parameter to customize the pid file setting
Fixed
- rsync-daemon package is now automatically installed in CentOS8 when xinetd is disabled.
Unsupported Release 1.1.1
Summary
This minor release is to roll out a bug fix.
Fixed
- Duplicate line removed from template.
- Small documentation fix.
Unsupported Release 1.1.0
Summary
This minor release is a roll up of bug fixes and features.
Added
- migrate to
rspec-puppet-facts
. - Add support for module
log file
. - Added module options that are currently missing.
Fixed
- Change redirects during fixtures download.
- Add upper version boundary for
xinted
dependency. - Replace legacy facts with new $facts hash.
Unsupported Release 1.0.0
Summary
This is a major release that drops Puppet 3 support.
Added
transfer_logging
andlog_format
parameters- Now optional management of rsync install with new
manage_package
parameter - Support for configuration via Hiera
- FreeBSD, RedHat family compatibility
- Make rsync::get compatible with
strict_variables
(MODULES-3515) ignore_nonreadable
parameter- Support for changing exclude/include order
chmod
andlogfile
parameters.sync.yml
added for modulesync compatibility
Changed
- Bumps puppetlabs-stdlib dependency up to 4.2.0
Fixed
- Replace .to_a with Kernel#Array (MODULES-1858)
2015-01-20 - Release 0.4.0
Summary
This release includes several new parameters and improvements.
Features
- Update
$include
and$exclude
to support arrays - Updated to use puppetlabs/concat instead of execs to build file!
- New parameters
- rsync::get
$options
$onlyif
- rsync::put
$include
$options
- rsync::server::module
$order
$refuse_options
- rsync::get
Bugfixes
- Fix auto-chmod of incoming and outgoing files when
incoming_chmod
oroutgoing_chmod
is set to false
2014-07-15 - Release 0.3.1
Summary
This release merely updates metadata.json so the module can be uninstalled and upgraded via the puppet module command.
2014-06-18 - Release 0.3.0
Features
- Added rsync::put defined type.
- Added
recursive
,links
,hardlinks
,copylinks
,times
andinclude
parameters to rsync::get. - Added
uid
andgid
parameters to rsync::server - Improved support for Debian
- Added
exclude
parameter to rsync::server::module
Bugfixes
- Added /usr/local/bin to path for the rsync command exec.
2013-01-31 - Release 0.2.0
- Added use_chroot parameter.
- Ensure rsync package is installed.
- Compatibility changes for Ruby 2.0.
- Added execuser parameter to run command as specified user.
- Various typo and bug fixes.
2012-06-07 - Release 0.1.0
- Initial release
Dependencies
- puppetlabs/stdlib (>=4.2.0 <9.0.0)
- puppetlabs/xinetd (>=1.1.0 < 4.0.0)
- puppetlabs/concat (>= 1.1.1 <7.0.0)
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.