With one monolithic playbook you can use task files for specific tasks just to
break up the "long" file.
- name: task 1 tasks
include_tasks: taskfile1.yml
- name: task 2 tasks
include_tasks: taskfile2.yml
- name: task 3 tasks
include_tasks: taskfile3.yml
- name: task 4 tasks
include_tasks: taskfile4.yml
We do this for our server provisioning. The task files can be short or long
depending on what they do. In some cases we use roles because they are used
also in other playbooks. You main playbook looks cleaner this way and it lets
you add items as you mature your service by simply developing the role or task
file and adding another stanza like these.
- name: install packages
include_tasks: ./common/packages.yml
- name: create local users and groups
include_tasks: ./common/users_groups.yml
- name: join to active directory
include_role:
name: nist-sssd-role
- name: configure volumes and filesystems
include_tasks: ./common/volumes.yml
Hope that helps.
Walter
--
Walter Rowe, Division Chief
Infrastructure Services, OISM
--
You received this message because you are subscribed to the Google Groups
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to ansible-project+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/ansible-project/7C270F4B-0A5F-4726-89C6-358FB95A5311%40nist.gov.
