clarifies FAQ answer about env vars (#48432)
This commit is contained in:
parent
46fa68ac27
commit
d27d956d71
2 changed files with 9 additions and 7 deletions
|
@ -401,14 +401,14 @@ For environment variables on the TARGET machines, they are available via facts i
|
||||||
|
|
||||||
{{ ansible_env.SOME_VARIABLE }}
|
{{ ansible_env.SOME_VARIABLE }}
|
||||||
|
|
||||||
If you need to set environment variables for TASK execution, see the Advanced Playbooks section about environments.
|
If you need to set environment variables for TASK execution, see :ref:`playbooks_environment` in the :ref:`Advanced Playbooks <playbooks_special_topics>` section.
|
||||||
There is no set way to set environment variables on your target machines, you can use template/replace/other modules to do so,
|
There are several ways to set environment variables on your target machines. You can use the :ref:`template <template_module>`, :ref:`replace <replace_module>`, or :ref:`lineinfile <lineinfile_module>` modules to introduce environment variables into files.
|
||||||
but the exact files to edit vary depending on your OS and distribution and local configuration.
|
The exact files to edit vary depending on your OS and distribution and local configuration.
|
||||||
|
|
||||||
.. _user_passwords:
|
.. _user_passwords:
|
||||||
|
|
||||||
How do I generate crypted passwords for the user module?
|
How do I generate encrypted passwords for the user module?
|
||||||
++++++++++++++++++++++++++++++++++++++++++++++++++++++++
|
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
|
||||||
|
|
||||||
Ansible ad-hoc command is the easiest option:
|
Ansible ad-hoc command is the easiest option:
|
||||||
|
|
||||||
|
|
|
@ -1,3 +1,5 @@
|
||||||
|
.. _playbooks_special_topics:
|
||||||
|
|
||||||
Advanced Playbooks Features
|
Advanced Playbooks Features
|
||||||
===========================
|
===========================
|
||||||
|
|
||||||
|
|
Loading…
Reference in a new issue