From 0a4c5701530526a1ba5abee50c5d202a5cfb8fe7 Mon Sep 17 00:00:00 2001 From: acrewdson Date: Wed, 19 Jul 2017 08:33:04 -0400 Subject: [PATCH] Fix typo (#26988) --- docs/docsite/rst/playbooks_vault.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/docsite/rst/playbooks_vault.rst b/docs/docsite/rst/playbooks_vault.rst index 99ca6a05ede..48eb2dbe6c0 100644 --- a/docs/docsite/rst/playbooks_vault.rst +++ b/docs/docsite/rst/playbooks_vault.rst @@ -136,7 +136,7 @@ As of version 2.3, Ansible can now use a vaulted variable that lives in an other other_plain_text: othervalue -This vaulted variable be decrypted with the supplied vault secret and used as a normal variable. The ``ansible-vault`` command line supports stdin and stdout for encrypting data on the fly, which can be used from your favorite editor to create these vaulted variables; you just have to be sure to add the ``!vault`` tag so both Ansible and YAML are aware of the need to decrypt. The ``|`` is also required, as vault encryption results in a multi-line string. +This vaulted variable will be decrypted with the supplied vault secret and used as a normal variable. The ``ansible-vault`` command line supports stdin and stdout for encrypting data on the fly, which can be used from your favorite editor to create these vaulted variables; you just have to be sure to add the ``!vault`` tag so both Ansible and YAML are aware of the need to decrypt. The ``|`` is also required, as vault encryption results in a multi-line string. .. _speeding_up_vault: