September 2018
Beginner to intermediate
214 pages
5h 53m
English
When making a playbook, using the name: field is optional. If you write a playbook with no name, it will work perfectly fine. The following is an example of a playbook that does not have a name:
---- hosts: servers become: yes gather_facts: false tasks: - apt: update_cache=yes - apt: name: mc - file: path: /usr/local/projects mode: 1777 state: directory
This playbook may have an output that looks as follows:

The playbook has done what we have asked it to do, but the fact that it doesn't have a name may present a problem if we have many tasks in one playbook because we won't be able to monitor the status of each job ...
Read now
Unlock full access