conf.dstyle structure where it is easy to build up the configuration from multiple sources.
assemblewill take a directory of files that can be local or have already been transferred to the system, and concatenate them together to produce a destination file. Files are assembled in string sorting order. Puppet calls this idea fragments.
(added in 2.3)
Attributes the file or directory should have. To get supported flags look at the man page for chattr on the target system. This string should contain the attributes in the same order as the one displayed by lsattr.
Create a backup file (if
(added in 1.4)
A delimiter to separate the file contents.
A file to create using the concatenation of all of the source files.
Name of the group that should own the file/directory, as would be fed to chown.
(added in 2.0)
A boolean that controls if files that start with a '.' will be included or not.
Mode the file or directory should be. For those used to /usr/bin/chmod remember that modes are actually octal numbers (like 0644). Leaving off the leading zero will likely have unexpected results. As of version 1.8, the mode may be specified as a symbolic mode (for example,
Name of the user that should own the file/directory, as would be fed to chown.
Assemble files only if
(added in 1.4)
If False, it will search for src at originating/master machine, if True it will go to the remote/target machine for the src. Default is True.
Level part of the SELinux file context. This is the MLS/MCS attribute, sometimes known as the
Role part of SELinux file context,
Type part of SELinux file context,
User part of SELinux file context. Will default to system policy, if applicable. If set to
An already existing directory full of source files.
(added in 2.2)
Normally this module uses atomic operations to prevent data corruption or inconsistent reads from the target files, sometimes systems are configured or just broken in ways that prevent this. One example are docker mounted files, they cannot be updated atomically and can only be done in an unsafe manner.
This boolean option allows ansible to fall back to unsafe methods of updating files for those cases in which you do not have any other choice. Be aware that this is subject to race conditions and can lead to data corruption.
(added in 2.0)
The validation command to run before copying into place. The path to the file to validate is passed in via '%s' which must be present as in the sshd example below. The command is passed securely so shell features like expansion and pipes won't work.
# Example from Ansible Playbooks - assemble: src: /etc/someapp/fragments dest: /etc/someapp/someapp.conf # When a delimiter is specified, it will be inserted in between each fragment - assemble: src: /etc/someapp/fragments dest: /etc/someapp/someapp.conf delimiter: '### START FRAGMENT ###' # Copy a new "sshd_config" file into place, after passing validation with sshd - assemble: src: /etc/ssh/conf.d/ dest: /etc/ssh/sshd_config validate: '/usr/sbin/sshd -t -f %s'
This module is flagged as stableinterface which means that the maintainers for this module guarantee that no backward incompatible interface changes will be made.