Assembles a configuration file from fragments. Often a particular program will take a single configuration file and does not support a conf.d style structure where it is easy to build up the configuration -from multiple sources. Assmeble will take a directory of files that +from multiple sources. Assemble will take a directory of files that 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”.
@@ -435,7 +435,13 @@ sorting order. Puppet calls this idea “fragments”.Example action from Ansible Playbooks:
copy src=/srv/myfiles/foo.conf dest=/etc/foo.conf owner=foo group=foo mode=0644
Copy a new ntp.conf file into place, backing up the original if it differs from the copied version:
+copy src=/srv/myfiles/ntp.conf dest=/etc/ntp.conf owner=root group=root mode=644 backup=yes
+Example action from Ansible Playbooks:
@@ -1183,7 +1204,7 @@ finally fall back to using the MySQL default login of ‘root’ with noExample action from Ansible Playbooks:
- name: Create database user
- action: mysql_user name=bob passwd=12345 priv=*.*:ALL state=present
+ action: mysql_user name=bob password=12345 priv=*.*:ALL state=present
- name: Ensure no user named 'sally' exists, also passing in the auth credentials.
action: mysql_user login_user=root login_password=123456 name=sally state=absent
@@ -1591,12 +1612,12 @@ happened and separately if the user was removed or not.
Example action from Ansible Playbooks:
- name: Create django user and grant access to database and products table
- postgresql_user db=acme user=django password=ceec4eif7ya privs=CONNECT/products:ALL
+ postgresql_user db=acme user=django password=ceec4eif7ya priv=CONNECT/products:ALL
- name: Remove test user privileges from acme
- postgresql_user db=acme user=test privs=ALL/products:ALL state=absent fail_on_user=no
+ postgresql_user db=acme user=test priv=ALL/products:ALL state=absent fail_on_user=no
- name: Remove test user from test database and the cluster
- postgresql_user db=test user=test privs=ALL state=absent
+ postgresql_user db=test user=test priv=ALL state=absent
Configures the SELinux mode and policy. A reboot may be required after usage. Ansible will not issue this reboot but will let you know when it is required.
-| parameter | -required | -default | -comments | -
|---|---|---|---|
| policy | -yes | -- | name of the SELinux policy to use (example: ‘targeted’) | -
| state | -yes | -- | the SELinux mode. ‘enforcing’, ‘permissive’, or ‘disabled’ | -
| conf | -no | -/etc/selinux/config | -path to the SELinux configuration file, if non-standard | -
Example from Ansible Playbooks:
selinux policy=targeted state=enforcing
selinux policy=targeted state=disabled
@@ -2013,6 +2002,10 @@ discarded. If no, this module will fail if it encounters modified files.
Templates a file out to a remote server.
+Templates are processed by the +Jinja2 templating language - +documentation on the template formatting can be found in the +Template Designer Documentation
| Location to render the template on the remote server | -||||
| OTHERS | +||||
| backup | +no | +no | +Create a backup file including the timestamp information so you can +get the original file back if you somehow clobbered it incorrectly. | +|
| OTHERS | This module also supports all of the arguments to the file module | @@ -2139,12 +2138,12 @@ system account. This setting cannot be changed on existing users.|||
| remove | no | -when used with state=remove, behavior is as with userdel –remove | +when used with state=absent, behavior is as with userdel –remove |
Example action from Ansible Playbooks:
-user name=mdehaan comment=awesome passwd=awWxVV.JvmdHw createhome=yes
+user name=mdehaan comment=awesome password=awWxVV.JvmdHw createhome=yes
user name=mdehaan groups=wheel,skynet
user name=mdehaan state=absent force=yes
@@ -2368,4 +2367,4 @@ yum name=httpd state=installed