2012-07-14 17:59:12 +02:00
|
|
|
# this is a virtual module that is entirely implemented server side
|
2012-09-29 00:49:02 +02:00
|
|
|
|
|
|
|
DOCUMENTATION = '''
|
|
|
|
---
|
|
|
|
module: template
|
2013-11-19 00:55:49 +01:00
|
|
|
version_added: historical
|
2012-09-29 00:49:02 +02:00
|
|
|
short_description: Templates a file out to a remote server.
|
|
|
|
description:
|
|
|
|
- Templates are processed by the Jinja2 templating language
|
|
|
|
(U(http://jinja.pocoo.org/docs/)) - documentation on the template
|
|
|
|
formatting can be found in the Template Designer Documentation
|
|
|
|
(U(http://jinja.pocoo.org/docs/templates/)).
|
2013-01-04 07:26:11 +01:00
|
|
|
- "Six additional variables can be used in templates: C(ansible_managed)
|
2012-10-23 15:14:01 +02:00
|
|
|
(configurable via the C(defaults) section of C(ansible.cfg)) contains a string
|
|
|
|
which can be used to describe the template name, host, modification time of the
|
|
|
|
template file and the owner uid, C(template_host) contains the node name of
|
2013-01-04 07:26:11 +01:00
|
|
|
the template's machine, C(template_uid) the owner, C(template_path) the
|
2013-10-08 14:40:22 +02:00
|
|
|
absolute path of the template, C(template_fullpath) is the absolute path of the
|
2014-02-15 20:13:42 +01:00
|
|
|
template, and C(template_run_date) is the date that the template was rendered. Note that including
|
2014-03-15 08:04:38 +01:00
|
|
|
a string that uses a date in the template will result in the template being marked 'changed'
|
2014-02-15 20:13:42 +01:00
|
|
|
each time."
|
2012-09-29 00:49:02 +02:00
|
|
|
options:
|
|
|
|
src:
|
|
|
|
description:
|
|
|
|
- Path of a Jinja2 formatted template on the local server. This can be a relative or absolute path.
|
|
|
|
required: true
|
|
|
|
default: null
|
|
|
|
aliases: []
|
|
|
|
dest:
|
|
|
|
description:
|
|
|
|
- Location to render the template to on the remote machine.
|
|
|
|
required: true
|
|
|
|
default: null
|
|
|
|
backup:
|
|
|
|
description:
|
|
|
|
- Create a backup file including the timestamp information so you can get
|
|
|
|
the original file back if you somehow clobbered it incorrectly.
|
|
|
|
required: false
|
|
|
|
choices: [ "yes", "no" ]
|
|
|
|
default: "no"
|
2013-03-27 04:12:56 +01:00
|
|
|
validate:
|
|
|
|
description:
|
2014-03-28 16:21:41 +01:00
|
|
|
- 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 visudo example below.
|
2014-03-24 16:06:25 +01:00
|
|
|
- validation to run before copying into place. The command is passed
|
|
|
|
securely so shell features like expansion and pipes won't work.
|
2013-03-27 04:12:56 +01:00
|
|
|
required: false
|
|
|
|
default: ""
|
|
|
|
version_added: "1.2"
|
2012-10-01 09:18:54 +02:00
|
|
|
notes:
|
2014-01-02 23:36:52 +01:00
|
|
|
- "Since Ansible version 0.9, templates are loaded with C(trim_blocks=True)."
|
2013-05-16 17:13:18 +02:00
|
|
|
requirements: []
|
2012-09-29 00:49:02 +02:00
|
|
|
author: Michael DeHaan
|
|
|
|
'''
|
2013-06-14 11:53:43 +02:00
|
|
|
|
|
|
|
EXAMPLES = '''
|
|
|
|
# Example from Ansible Playbooks
|
|
|
|
- template: src=/mytemplates/foo.j2 dest=/etc/file.conf owner=bin group=wheel mode=0644
|
|
|
|
|
2014-03-26 18:42:15 +01:00
|
|
|
# Copy a new "sudoers" file into place, after passing validation with visudo
|
|
|
|
- template: src=/mine/sudoers dest=/etc/sudoers validate='visudo -cf %s'
|
2013-06-14 11:53:43 +02:00
|
|
|
'''
|