Ansible’s template module transfers templated files to remote hosts. It works similarly to the copy module, but with 2 major differences: The template module is extremely useful for doing machine-specific configuration based on Ansible variables. Given the following file structure: ├── ansible.cfg ├── templates │ └── my_app.conf.j2

The template module is how Ansible generates files dynamically on your servers. By combining templates with variables and logic, you take your automation to the next level. In this in-depth guide, you‘ll learn how to create flexible playbooks with the template module and Jinja2 templating language.

Additional variables listed below can be used in templates. ansible_managed (configurable via the defaults section of 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. template_host contains the node name of the template’s machine.

Templates have the following properties: Optional. This name is used when selecting a template to create from. If this property is empty, the template will not be shown in the template selector (this can be useful if you create templates that are just for inheritance). Optional. A path relative to the workspace root.