ansible/community.general
1
0
Fork 0
mirror of https://github.com/ansible-collections/community.general.git synced 2024-09-14 20:13:21 +02:00
Code Releases Activity

Minor tweaks to the skipped config wording and adding documentation

Browse source
This commit is contained in:
James Cammarata 2013-09-30 21:02:09 -05:00
parent 6cd8aacc81
commit c8fa83c93f
2 changed files with 13 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

9
docsite/latest/rst/intro_configuration.rst
View file

@ -109,6 +109,15 @@ different locations::
Most users will not need to use this feature. See `developing_plugins` for more details
display_skipped_hosts
=====================
If set to `False`, ansible will not display any status for a task that is skipped. The default behavior is to display skipped tasks::
#display_skipped_hosts=True
Note that Ansible will always show the task header for any task, regardless of whether or not the task is skipped.
error_on_undefined_vars
=======================

7
examples/ansible.cfg
View file

@ -73,9 +73,10 @@ timeout = 10
ansible_managed = Ansible managed: {file} modified on %Y-%m-%d %H:%M:%S by {uid} on {host}
# by default, ansible-playbook will display "Skipping [host]" if it determines a task
# should not be run on a host. Set this to "no" if you don't want to see these "Skipping"
# messages.
# display_skipped_hosts: yes
# should not be run on a host. Set this to "False" if you don't want to see these "Skipping"
# messages. NOTE: the task header will still be shown regardless of whether or not the
# task is skipped.
#display_skipped_hosts = True
# by default (as of 1.3), Ansible will raise errors when attempting to dereference
# Jinja2 variables that are not set in templates or action lines. Uncomment this line