80e7e1a17c
* Due to the takeover of freenode we're moving to a different irc network. * Our channels updated to point at the same channel name on libera.chat * Some links went to webchat.freenode.net. At this time, libera.chat doesn't point you to an official webchat client so I changed these to https://libera.chat. (kiwi irc does work with libera.chat so that could be another option). * In general, I used the name irc.libera.net for link names and https://libera.chat for link targets. This is because the irc service is hosted on irc.libera.chat but the project web server is hosted on libera.chat. (This appears to also be true for freenode but we were using http://irc.freenode.net which doesn't seem to work. Oops). * Removed http://irc.freenode.net from the linkcheck exceptions. linkcheck was actually correct to flag that as invalid (should have been http://frenode.net instead). * Looks like hte important people in #yaml are now in libera.chat * Link to where contributors should get help Add a link target and then link to where contributors should get support for developing groups of modules. * Update docs/docsite/rst/dev_guide/developing_modules_in_groups.rst Co-authored-by: Felix Fontein <felix@fontein.de> Co-authored-by: John R Barker <john@johnrbarker.com> Co-authored-by: Felix Fontein <felix@fontein.de>
53 lines
1.8 KiB
ReStructuredText
53 lines
1.8 KiB
ReStructuredText
.. _shell_plugins:
|
|
|
|
Shell Plugins
|
|
=============
|
|
|
|
.. contents::
|
|
:local:
|
|
:depth: 2
|
|
|
|
Shell plugins work to ensure that the basic commands Ansible runs are properly formatted to work with
|
|
the target machine and allow the user to configure certain behaviors related to how Ansible executes tasks.
|
|
|
|
.. _enabling_shell:
|
|
|
|
Enabling shell plugins
|
|
----------------------
|
|
|
|
You can add a custom shell plugin by dropping it into a ``shell_plugins`` directory adjacent to your play, inside a role,
|
|
or by putting it in one of the shell plugin directory sources configured in :ref:`ansible.cfg <ansible_configuration_settings>`.
|
|
|
|
.. warning:: You should not alter which plugin is used unless you have a setup in which the default ``/bin/sh``
|
|
is not a POSIX compatible shell or is not available for execution.
|
|
|
|
.. _using_shell:
|
|
|
|
Using shell plugins
|
|
-------------------
|
|
|
|
In addition to the default configuration settings in :ref:`ansible_configuration_settings`, you can use
|
|
the connection variable :ref:`ansible_shell_type <ansible_shell_type>` to select the plugin to use.
|
|
In this case, you will also want to update the :ref:`ansible_shell_executable <ansible_shell_executable>` to match.
|
|
|
|
You can further control the settings for each plugin via other configuration options
|
|
detailed in the plugin themselves (linked below).
|
|
|
|
.. seealso::
|
|
|
|
:ref:`about_playbooks`
|
|
An introduction to playbooks
|
|
:ref:`inventory_plugins`
|
|
Ansible inventory plugins
|
|
:ref:`callback_plugins`
|
|
Ansible callback plugins
|
|
:ref:`playbooks_filters`
|
|
Jinja2 filter plugins
|
|
:ref:`playbooks_tests`
|
|
Jinja2 test plugins
|
|
:ref:`playbooks_lookups`
|
|
Jinja2 lookup plugins
|
|
`User Mailing List <https://groups.google.com/group/ansible-devel>`_
|
|
Have a question? Stop by the google group!
|
|
`irc.libera.chat <https://libera.chat/>`_
|
|
#ansible IRC chat channel
|