mirror of
https://github.com/ansible-collections/community.general.git
synced 2025-10-21 11:34:15 -07:00
Add a configuration setting that allows the user to specify printing of task arguments in the header.
Fixes #14554
This commit is contained in:
parent
54942ee8ff
commit
86b8dc0e79
4 changed files with 53 additions and 3 deletions
|
@ -304,8 +304,6 @@ How do I keep secret data in my playbook?
|
|||
|
||||
If you would like to keep secret data in your Ansible content and still share it publicly or keep things in source control, see :doc:`playbooks_vault`.
|
||||
|
||||
.. _i_dont_see_my_question:
|
||||
|
||||
In Ansible 1.8 and later, if you have a task that you don't want to show the results or command given to it when using -v (verbose) mode, the following task or playbook attribute can be useful::
|
||||
|
||||
- name: secret task
|
||||
|
@ -323,6 +321,8 @@ Though this will make the play somewhat difficult to debug. It's recommended th
|
|||
be applied to single tasks only, once a playbook is completed.
|
||||
|
||||
|
||||
.. _i_dont_see_my_question:
|
||||
|
||||
I don't see my question here
|
||||
++++++++++++++++++++++++++++
|
||||
|
||||
|
|
|
@ -228,6 +228,34 @@ Allows disabling of deprecating warnings in ansible-playbook output::
|
|||
|
||||
Deprecation warnings indicate usage of legacy features that are slated for removal in a future release of Ansible.
|
||||
|
||||
.. _display_args_to_stdout
|
||||
|
||||
display_args_to_stdout
|
||||
======================
|
||||
|
||||
.. versionadded:: 2.1.0
|
||||
|
||||
By default, ansible-playbook will print a header for each task that is run to
|
||||
stdout. These headers will contain the ``name:`` field from the task if you
|
||||
specified one. If you didn't then ansible-playbook uses the task's action to
|
||||
help you tell which task is presently running. Sometimes you run many of the
|
||||
same action and so you want more information about the task to differentiate
|
||||
it from others of the same action. If you set this variable to ``True`` in
|
||||
the config then ansible-playbook will also include the task's arguments in the
|
||||
header.
|
||||
|
||||
This setting defaults to ``False`` because there is a chance that you have
|
||||
sensitive values in your parameters and do not want those to be printed to
|
||||
stdout::
|
||||
|
||||
display_args_to_stdout=False
|
||||
|
||||
If you set this to ``True`` you should be sure that you have secured your
|
||||
environment's stdout (no one can shoulder surf your screen and you aren't
|
||||
saving stdout to an insecure file) or made sure that all of your playbooks
|
||||
explicitly added the ``no_log: True`` parameter to tasks which have sensistive
|
||||
values See :ref:`keep_secret_data` for more information.
|
||||
|
||||
.. _display_skipped_hosts:
|
||||
|
||||
display_skipped_hosts
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue