From b1f02be9eb68247d21dfa48fcc824479708edf12 Mon Sep 17 00:00:00 2001 From: Christian Adams Date: Mon, 4 Nov 2019 18:47:03 -0500 Subject: [PATCH] clarify vault warning and fix typo (#64419) --- docs/docsite/rst/user_guide/playbooks_vault.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/docsite/rst/user_guide/playbooks_vault.rst b/docs/docsite/rst/user_guide/playbooks_vault.rst index 8a80f81bda8..522d58817e4 100644 --- a/docs/docsite/rst/user_guide/playbooks_vault.rst +++ b/docs/docsite/rst/user_guide/playbooks_vault.rst @@ -22,7 +22,7 @@ There are 2 types of vaulted content and each has their own uses and limitations * You can mix vaulted and non vaulted variables in the same file, even inline in a play or role. .. warning:: - * Vault ONLY protects data 'at rest', once decrypted play and plugin authors are responsible of avoiding any secrets discolsure, + * Vault ONLY protects data 'at rest'. Once decrypted, play and plugin authors are responsible for avoiding any secret disclosure, see :ref:`no_log ` for details on hiding output. To enable this feature, a command line tool, :ref:`ansible-vault` is used to edit files, and a command line flag :option:`--ask-vault-pass `, :option:`--vault-password-file ` or :option:`--vault-id ` is used. You can also modify your ``ansible.cfg`` file to specify the location of a password file or configure Ansible to always prompt for the password. These options require no command line flag usage.