ansible-collections/community.general
1
0
Fork 0
mirror of https://github.com/ansible-collections/community.general.git synced 2025-10-22 20:13:59 -07:00
Code Issues Projects Releases Packages Wiki Activity Actions 4

Fix documentation syntax problems

Browse source
This commit is contained in:
Toshio Kuratomi 2014-12-16 12:25:41 -08:00
commit b74a02301b
5 changed files with 7 additions and 9 deletions
Download patch file Download diff file Expand all files Collapse all files

6
docsite/rst/playbooks_best_practices.rst
View file

@ -66,9 +66,7 @@ The top level of the directory would contain files and directories like so::
monitoring/ # ""
fooapp/ # ""
.. note: If you find yourself having too many top level playbooks (for instance you have a playbook you wrote for a specific hotfix, etc), it may
make sense to have a playbooks/ directory instead. This can be a good idea as you get larger. If you do this,
configure your roles_path in ansible.cfg to find your roles location.
.. note: If you find yourself having too many top level playbooks (for instance you have a playbook you wrote for a specific hotfix, etc), it may make sense to have a playbooks/ directory instead. This can be a good idea as you get larger. If you do this, configure your roles_path in ansible.cfg to find your roles location.
.. _use_dynamic_inventory_with_clouds:
@ -367,7 +365,7 @@ If group-specific settings are needed, this can also be done. For example::
In the above example, CentOS machines get the value of '42' for asdf, but other machines get '10'.
This can be used not only to set variables, but also to apply certain roles to only certain systems.
Alternatively, if only variables are needed:
Alternatively, if only variables are needed::
- hosts: all
tasks: