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>
2.1 KiB
Become Plugins
2.8
Become plugins work to ensure that Ansible can use certain privilege escalation systems when running the basic commands to work with the target machine as well as the modules required to execute the tasks specified in the play.
These utilities (sudo, su,
doas, and so on) generally let you 'become' another user to
execute a command with the permissions of that user.
Enabling Become Plugins
The become plugins shipped with Ansible are already enabled. Custom
plugins can be added by placing them into a become_plugins
directory adjacent to your play, inside a role, or by placing them in
one of the become plugin directory sources configured in ansible.cfg <ansible_configuration_settings>.
Using Become Plugins
In addition to the default configuration settings in ansible_configuration_settings or the
--become-method command line option, you can use the
become_method keyword in a play or, if you need to be 'host
specific', the connection variable ansible_become_method to
select the plugin to use.
You can further control the settings for each plugin via other configuration options detailed in the plugin themselves (linked below).
Plugin List
You can use ansible-doc -t become -l to see the list of
available plugins. Use
ansible-doc -t become <plugin name> to see specific
documentation and examples.
about_playbooks-
An introduction to playbooks
inventory_plugins-
Ansible inventory plugins
callback_plugins-
Ansible callback plugins
playbooks_filters-
Jinja2 filter plugins
playbooks_tests-
Jinja2 test plugins
playbooks_lookups-
Jinja2 lookup plugins
- User Mailing List
-
Have a question? Stop by the google group!
- irc.libera.chat
-
#ansible IRC chat channel