You can include playbooks now.
This commit is contained in:
parent
47eea55d13
commit
85277e9e64
1 changed files with 0 additions and 8 deletions
|
@ -68,14 +68,6 @@ when things change, and these are described in :doc:`playbooks`.
|
||||||
|
|
||||||
Including more than one setup file or more than one handlers file is of course legal.
|
Including more than one setup file or more than one handlers file is of course legal.
|
||||||
|
|
||||||
Having playbooks be able to include other playbooks is coming in a
|
|
||||||
future release. See `Issue 538
|
|
||||||
<https://github.com/ansible/ansible/issues/538>`_.
|
|
||||||
|
|
||||||
Until then, to manage your entire site, simply execute all of your playbooks together, in the order desired.
|
|
||||||
You don't have to do this though. It's fine to select sections of your infrastructure to manage at a single time.
|
|
||||||
You may wish to construct simple shell scripts to wrap calls to ansible-playbook.
|
|
||||||
|
|
||||||
Bundling Ansible Modules With Playbooks
|
Bundling Ansible Modules With Playbooks
|
||||||
+++++++++++++++++++++++++++++++++++++++
|
+++++++++++++++++++++++++++++++++++++++
|
||||||
|
|
||||||
|
|
Loading…
Reference in a new issue