Parameter |
Choices/Defaults |
Comments |
attributes
(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.
= operator is assumed as default, otherwise + or - operators need to be included in the string.
aliases: attr
|
backup
bool |
|
Create a backup file including the timestamp information so you can get the original file back if you somehow clobbered it incorrectly.
|
dest
|
Default:
/etc/network/interfaces
|
Path to the interfaces file
|
group
|
|
Name of the group that should own the file/directory, as would be fed to chown.
|
iface
|
|
Name of the interface, required for value changes or option remove
|
mode
|
|
Mode the file or directory should be. For those used to /usr/bin/chmod remember that modes are actually octal numbers. You must either add a leading zero so that Ansible's YAML parser knows it is an octal number (like 0644 or 01777 ) or quote it (like '644' or '1777' ) so Ansible receives a string and can do its own conversion from string into number. Giving Ansible a number without following one of these rules will end up with a decimal number which will have unexpected results. As of version 1.8, the mode may be specified as a symbolic mode (for example, u+rwx or u=rw,g=r,o=r ).
|
option
|
|
Name of the option, required for value changes or option remove
|
owner
|
|
Name of the user that should own the file/directory, as would be fed to chown.
|
selevel
|
Default:
s0
|
Level part of the SELinux file context. This is the MLS/MCS attribute, sometimes known as the range . _default feature works as for seuser.
|
serole
|
|
Role part of SELinux file context, _default feature works as for seuser.
|
setype
|
|
Type part of SELinux file context, _default feature works as for seuser.
|
seuser
|
|
User part of SELinux file context. Will default to system policy, if applicable. If set to _default , it will use the user portion of the policy if available.
|
state
|
Choices:
present ←
- absent
|
If set to absent the option or section will be removed if present instead of created.
|
unsafe_writes
bool
(added in 2.2) |
|
By default this module uses atomic operations to prevent data corruption or inconsistent reads from the target files, but sometimes systems are configured or just broken in ways that prevent this. One example is docker mounted files, which cannot be updated atomically from inside the container and can only be written in an unsafe manner.
This option allows Ansible to fall back to unsafe methods of updating files when atomic operations fail (however, it doesn't force Ansible to perform unsafe writes). IMPORTANT! Unsafe writes are subject to race conditions and can lead to data corruption.
|
value
|
|
If option is not presented for the interface and state is present option will be added. If option already exists and is not pre-up , up , post-up or down , it's value will be updated. pre-up , up , post-up and down options can't be updated, only adding new options, removing existing ones or cleaning the whole option set are supported
|