summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorAbhijeet Kasurde <akasurde@redhat.com>2021-06-25 00:02:20 +0530
committerGitHub <noreply@github.com>2021-06-24 13:32:20 -0500
commit50ef1599a1fd745afe37f4a249e3e664f41436c8 (patch)
treef06d26354d232478e48fdf6160821bd90ed28517
parent2c2e168eff5747f8ef75d3695280698123e6a8ce (diff)
downloadansible-50ef1599a1fd745afe37f4a249e3e664f41436c8.tar.gz
[bp-2.10] Clarify Vault password client naming requirements (#75082)
(cherry picked from commit aedc82da9825b6c687cbff36a94c6a065f8af5f8) Co-authored-by: Andreas Olsson <andreas@arrakis.se>
-rw-r--r--docs/docsite/rst/user_guide/vault.rst2
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/docsite/rst/user_guide/vault.rst b/docs/docsite/rst/user_guide/vault.rst
index abb2fadb62..ef9bd855a0 100644
--- a/docs/docsite/rst/user_guide/vault.rst
+++ b/docs/docsite/rst/user_guide/vault.rst
@@ -94,7 +94,7 @@ You can store your vault passwords on the system keyring, in a database, or in a
To create a vault password client script:
- * Create a file with a name ending in ``-client.py``
+ * Create a file with a name ending in either ``-client`` or ``-client.EXTENSION``
* Make the file executable
* Within the script itself:
* Print the passwords to standard output