I'm trying to organize my playbooks according to the Directory Layout structure. The documentation doesn't seem to have a recommendation for host-specific files/templates.
I have 2 plays for a single site
- example.com-provision.yml
- example.com-deploy.yml
These files are located in the root of my structure. The provisioning playbook simply includes other roles
---
- hosts: example.com
roles:
- common
- application
- database
become: true
become_method: su
become_user: root
The deployment playbook doesn't include roles, but has it's own vars
and tasks
sections. I have a couple template
and copy
tasks, and am wondering what the 'best practice' is for where to put these host-specific templates/files within this directory structure.
Right now I have them at ./roles/example.com/templates/
and ./roles/example.com/files/
, but need to reference the files with their full path from my deployment playbook, like
- name: deployment | copy httpd config
template:
src: ./roles/example.com/templates/{{ host }}.conf.j2
# ...
instead of
- name: deployment | copy httpd config
template:
src: {{ host }}.conf.j2
# ...
Facing the same problem the cleanest way seems for me the following structure:
In the top-level directory (same level as playbooks) I have a
files
folder (and if I needed also atemplates
folder). In thefiles
folder there is a folder for every host with it's own files where the folder's name is the same as the host name in inventory. (see the structure below:myhost1
myhost2
)Now in any role you can access the files with files modules relatively:
Explanation:
The magic variable
inventory_hostname
is to get the host, see here The anyfile
module (as for examplecopy
) looks up thefiles
directory in the respective role directory and thefiles
directory in the same level as the calling playbook. Of course same applies to templates (but if you have different templates for the same role you should reconsider your design)Semantically a host specific file does not belong into a role, but somewhere outside (like
host_vars
).