cmueller/ansible
1
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

Fix typo and styling FAQ docs (#68212)

Browse source
This commit is contained in:
dirkvbok 2020-03-24 09:00:03 +01:00 committed by GitHub
parent fb2a7ce923
commit 4083514d3e
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 3 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

6
docs/docsite/rst/reference_appendices/faq.rst
View file

@ -396,7 +396,7 @@ Also see dynamic_variables_.
How do I access a group variable? How do I access a group variable?
+++++++++++++++++++++++++++++++++ +++++++++++++++++++++++++++++++++
Technically, you don't, Ansible does not really use groups directly. Groups are label for host selection and a way to bulk assign variables, they are not a first class entity, Ansible only cares about Hosts and Tasks. Technically, you don't, Ansible does not really use groups directly. Groups are labels for host selection and a way to bulk assign variables, they are not a first class entity, Ansible only cares about Hosts and Tasks.
That said, you could just access the variable by selecting a host that is part of that group, see first_host_in_a_group_ below for an example. That said, you could just access the variable by selecting a host that is part of that group, see first_host_in_a_group_ below for an example.
@ -596,14 +596,14 @@ If you have a task that you don't want to show the results or command given to i
This can be used to keep verbose output but hide sensitive information from others who would otherwise like to be able to see the output. This can be used to keep verbose output but hide sensitive information from others who would otherwise like to be able to see the output.
The no_log attribute can also apply to an entire play:: The ``no_log`` attribute can also apply to an entire play::
- hosts: all - hosts: all
no_log: True no_log: True
Though this will make the play somewhat difficult to debug. It's recommended that this Though this will make the play somewhat difficult to debug. It's recommended that this
be applied to single tasks only, once a playbook is completed. Note that the use of the be applied to single tasks only, once a playbook is completed. Note that the use of the
no_log attribute does not prevent data from being shown when debugging Ansible itself via ``no_log`` attribute does not prevent data from being shown when debugging Ansible itself via
the :envvar:`ANSIBLE_DEBUG` environment variable. the :envvar:`ANSIBLE_DEBUG` environment variable.