-
Notifications
You must be signed in to change notification settings - Fork 23.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
several FAQ updates and clarifications #41841
Conversation
|
||
.. code-block:: jinja | ||
|
||
{{ ansible_env.SOME_VARIABLE }} | ||
|
||
If you need to set environment variables for TASK execution, see the Advanced Playbooks section about environments. | ||
There is no set way to set environment variables on your target machines, you can use tempalte/replace/other modules to do so, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
typo here s/tempalte/template/g
Yes! Ansible, Inc makes a great product that makes Ansible even more powerful | ||
and easy to use. See :doc:`../reference_appendices/tower`. | ||
Yes! Ansible, Inc makes a great product that makes Ansible even more powerful and easy to use. See :doc:`../reference_appendices/tower`. | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should probably remove the "Ansible, Inc" reference if we're making changes to this line.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Red Hat inc?
so you can use this for custom modules written in any scripting language and control the interpreter location. | ||
|
||
Keep in mind that if you put `env` in your module shebang line (`#!/usr/bin/env <other>`), | ||
this facility will be ignored so you will be at the mercy of the remote `$PATH`. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not clear on the breadth of the warning about using env
in the shebang line - will that cause problems only with non-Python scripts/modules? Or will it disrupt the Ansible's ability to find any interpreter that is not on the connection user's $PATH?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
it will disrupt the usage of ansible_<interpreter>_interpreter
vars for any module that uses env
Useful additions, thanks. I've added a couple of minor comments. |
SUMMARY
ISSUE TYPE
COMPONENT NAME
faq
ANSIBLE VERSION