From b768a0780c1b175af5866d6bc2165b417b979ab8 Mon Sep 17 00:00:00 2001 From: Sayed Anisul Hoque Date: Tue, 18 Jun 2019 18:23:30 +0200 Subject: [PATCH] Update playbooks_vault.rst (#58005) Corrected the internal reference link to point to the FAQ entry. +label: docsite_pr --- 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 7890c1fe755..8a80f81bda8 100644 --- a/docs/docsite/rst/user_guide/playbooks_vault.rst +++ b/docs/docsite/rst/user_guide/playbooks_vault.rst @@ -23,7 +23,7 @@ There are 2 types of vaulted content and each has their own uses and limitations .. warning:: * Vault ONLY protects data 'at rest', once decrypted play and plugin authors are responsible of avoiding any secrets discolsure, - see ``no_log`` for details on hiding output. + 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.