mirror of
https://github.com/ansible-collections/community.general.git
synced 2026-05-07 13:52:54 +00:00
Fix places in docs that refer to modules without namespace
We've namespaced all plugin docs. Change the docs to reflect that
This commit is contained in:
@@ -150,8 +150,8 @@ Ways to resolve this include:
|
||||
* Use `pipelining`. When pipelining is enabled, Ansible doesn't save the
|
||||
module to a temporary file on the client. Instead it pipes the module to
|
||||
the remote python interpreter's stdin. Pipelining does not work for
|
||||
python modules involving file transfer (for example: :ref:`copy <copy>`,
|
||||
:ref:`fetch <fetch>`, :ref:`template <template>`), or for non-python modules.
|
||||
python modules involving file transfer (for example: :ref:`copy <copy_module>`,
|
||||
:ref:`fetch <fetch_module>`, :ref:`template <template_module>`), or for non-python modules.
|
||||
|
||||
* (Available in Ansible 2.1) Install POSIX.1e filesystem acl support on the
|
||||
managed host. If the temporary directory on the remote host is mounted with
|
||||
|
||||
@@ -19,8 +19,10 @@ Ansible Vault can encrypt any structured data file used by Ansible. This can in
|
||||
Ansible tasks, handlers, and so on are also data so these can be encrypted with vault as well. To hide the names of variables that you're using, you can encrypt the task files in their entirety.
|
||||
|
||||
Ansible Vault can also encrypt arbitrary files, even binary files. If a vault-encrypted file is
|
||||
given as the ``src`` argument to the :ref:`copy <copy>`, :ref:`template <template>`,
|
||||
:ref:`unarchive <unarchive>`, :ref:`script <script>` or :ref:`assemble <assemble>` modules, the file will be placed at the destination on the target host decrypted (assuming a valid vault password is supplied when running the play).
|
||||
given as the ``src`` argument to the :ref:`copy <copy_module>`, :ref:`template <template_module>`,
|
||||
:ref:`unarchive <unarchive_module>`, :ref:`script <script_module>` or :ref:`assemble
|
||||
<assemble_module>` modules, the file will be placed at the destination on the target host decrypted
|
||||
(assuming a valid vault password is supplied when running the play).
|
||||
|
||||
As of version 2.3, Ansible supports encrypting single values inside a YAML file, using the `!vault` tag to let YAML and Ansible know it uses special processing. This feature is covered in more details below.
|
||||
|
||||
|
||||
Reference in New Issue
Block a user