* Python interpreter discovery

* No longer blindly default to only `/usr/bin/python`
* `ansible_python_interpreter` defaults to `auto_legacy`, which will discover the platform Python interpreter on some platforms (but still favor `/usr/bin/python` if present for backward compatibility). Use `auto` to always use the discovered interpreter, append `_silent` to either value to suppress warnings.
* includes new doc utility method `get_versioned_doclink` to generate a major.minor versioned doclink against docs.ansible.com (or some other config-overridden URL)

* docs revisions for python interpreter discovery

(cherry picked from commit 5b53c0012ab7212304c28fdd24cb33fd8ff755c2)

* verify output on some distros, cleanup

2019-02-27 23:52:02 -08:00

1.2 KiB

Raw Blame History

Working With Modules

modules_intro ../reference_appendices/common_return_values modules_support ../modules/modules_by_category

Ansible ships with a number of modules (called the 'module library') that can be executed directly on remote hosts or through Playbooks <playbooks>.

Users can also write their own modules. These modules can control system resources, like services, packages, or files (anything really), or handle executing system commands.

intro_adhoc: Examples of using modules in /usr/bin/ansible
playbooks: Examples of using modules with /usr/bin/ansible-playbook
../dev_guide/developing_modules: How to write your own modules
../dev_guide/developing_api: Examples of using modules with the Python API
../reference_appendices/interpreter_discovery: Configuring the right Python interpreter on target hosts
Mailing List: Questions? Help? Ideas? Stop by the list on Google Groups
irc.freenode.net: #ansible IRC chat channel

1.2 KiB Raw Blame History

Working With Modules

1.2 KiB

Raw Blame History