ansible/docs/docsite/rst/playbooks.rst

Playbooks
`````````

Playbooks are Ansible's configuration, deployment, and orchestration language.  They can describe a policy you want your remote systems to enforce, or a set of steps in a general IT process.

If Ansible modules are the tools in your workshop, playbooks are your instruction manuals, and your inventory of hosts are your raw material.

At a basic level, playbooks can be used to manage configurations of and deployments to remote machines.  At a more advanced level, they can sequence multi-tier rollouts involving rolling updates, and can delegate actions to other hosts, interacting with monitoring servers and load balancers along the way.  

While there's a lot of information here, there's no need to learn everything at once.  You can start small and pick up more features
over time as you need them.  

Playbooks are designed to be human-readable and are developed in a basic text language.  There are multiple
ways to organize playbooks and the files they include, and we'll offer up some suggestions on that and making the most out of Ansible.

It is recommended to look at `Example Playbooks <https://github.com/ansible/ansible-examples>`_ while reading along with the playbook documentation.  These illustrate best practices as well as how to put many of the various concepts together.

.. toctree::
   :maxdepth: 1

   playbooks_intro
   playbooks_roles
   playbooks_variables
   playbooks_filters
   playbooks_tests
   playbooks_conditionals
   playbooks_loops
   playbooks_blocks
   playbooks_strategies
   playbooks_best_practices
Reorg of the documentation tree such that the sidebar will be more correct. Some work yet to do on module docs. 11 years ago			`Playbooks`
			`````````
Add some 1.1 feature documentation 12 years ago
Reorg of the documentation tree such that the sidebar will be more correct. Some work yet to do on module docs. 11 years ago			`Playbooks are Ansible's configuration, deployment, and orchestration language. They can describe a policy you want your remote systems to enforce, or a set of steps in a general IT process.`
More anchors! 11 years ago
I think that is a better analogy. 8 years ago			`If Ansible modules are the tools in your workshop, playbooks are your instruction manuals, and your inventory of hosts are your raw material.`
Update docs 13 years ago
Reorg of the documentation tree such that the sidebar will be more correct. Some work yet to do on module docs. 11 years ago			`At a basic level, playbooks can be used to manage configurations of and deployments to remote machines. At a more advanced level, they can sequence multi-tier rollouts involving rolling updates, and can delegate actions to other hosts, interacting with monitoring servers and load balancers along the way.`
Minor playbooks doc tweaks. 11 years ago
Reorg of the documentation tree such that the sidebar will be more correct. Some work yet to do on module docs. 11 years ago			`While there's a lot of information here, there's no need to learn everything at once. You can start small and pick up more features`
			`over time as you need them.`
Updating docs, added extensive info on playbook async + external vars_files for keeping variables outside of the playbook file. 13 years ago
Reorg of the documentation tree such that the sidebar will be more correct. Some work yet to do on module docs. 11 years ago			`Playbooks are designed to be human-readable and are developed in a basic text language. There are multiple`
			`ways to organize playbooks and the files they include, and we'll offer up some suggestions on that and making the most out of Ansible.`
Updating docs, added extensive info on playbook async + external vars_files for keeping variables outside of the playbook file. 13 years ago
Reorg of the documentation tree such that the sidebar will be more correct. Some work yet to do on module docs. 11 years ago			It is recommended to look at `Example Playbooks <https://github.com/ansible/ansible-examples>`_ while reading along with the playbook documentation. These illustrate best practices as well as how to put many of the various concepts together.
Updating docs, added extensive info on playbook async + external vars_files for keeping variables outside of the playbook file. 13 years ago
Reorg of the documentation tree such that the sidebar will be more correct. Some work yet to do on module docs. 11 years ago			`.. toctree::`
			`:maxdepth: 1`
Update docs 13 years ago
Re-add the playbook introduction which was replaced earlier. 11 years ago			`playbooks_intro`
Reorg of the documentation tree such that the sidebar will be more correct. Some work yet to do on module docs. 11 years ago			`playbooks_roles`
			`playbooks_variables`
Add the playbook filters to a toctree 10 years ago			`playbooks_filters`
J2 test docs (#16646) * moved tests from filters to actual jinja2 tests also removed some unused declarations and imports * split tests into their own docs removed isnan as existing jinja2's 'number' already covers same added missing docs for several tests * updated as per feedback 8 years ago			`playbooks_tests`
Reorg of the documentation tree such that the sidebar will be more correct. Some work yet to do on module docs. 11 years ago			`playbooks_conditionals`
			`playbooks_loops`
moar docs added docs for new v2 features restructures modules bar and core/extras info into their own pages changed templates to refer to the new pages added some missing ansible.cfg options more info on gathering setting 9 years ago			`playbooks_blocks`
			`playbooks_strategies`
Reorg of the documentation tree such that the sidebar will be more correct. Some work yet to do on module docs. 11 years ago			`playbooks_best_practices`
Added docs on conditional import usage 13 years ago
Docs updates 13 years ago