Toshio Kuratomi 9dda393d70

* Build documentation for Ansible-2.10 (formerly known as ACD).

Builds plugin docs from collections whose source is on galaxy

The new command downloads collections from galaxy, then finds the
plugins inside of them to get the documentation for those plugins.

* Update the python syntax checks
  * docs builds can now require python 3.6+.

* Move plugin formatter code out to an external tool, antsibull-docs.
  Collection owners want to be able to extract docs for their own
  websites as well.
* The jinja2 filters, tests, and other support code have moved to antsibull
* Remove document_plugins as that has now been integrated into antsibull-docs

* Cleanup and bugfix to other build script code:
  * The Commands class needed to have its metaclass set for abstractmethod
    to work correctly
  * Fix lint issues in some command plugins

* Add the docs/docsite/rst/collections to .gitignore as
  everything in that directory will be generated so we don't want any of
  it saved in the git repository
* gitignore the build dir and remove edit docs link on module pages

* Add docs/rst/collections as a directory to remove on make clean
* Split the collections docs from the main docs

* remove version and edit on github
* remove version banner for just collections
* clarify examples need collection keyword defined

* Remove references to plugin documentation locations that no longer exist.
  * Perhaps the pages in plugins/*.rst should be deprecated
    altogether and their content moved?
  * If not, perhaps we want to rephrase and link into the collection
    documentation?
  * Or perhaps we want to link to the plugins which are present in
    collections/ansible/builtin?

* Remove PYTHONPATH from the build-ansible calls
  One of the design goals of the build-ansible.py script was for it to
  automatically set its library path to include the checkout of ansible
  and the library of code to implement itself.  Because it automatically
  includes the checkout of ansible, we don't need to set PYTHONPATH in
  the Makefile any longer.

* Create a command to only build ansible-base plugin docs
  * When building docs for devel, only build the ansible-base docs for
    now.  This is because antsibull needs support for building a "devel
    tree" of docs.  This can be changed once that is implemented
  * When building docs for the sanity tests, only build the ansible-base
    plugin docs for now.  Those are the docs which are in this repo so
    that seems appropriate for now.

2020-07-17 13:07:35 -07:00

3.5 KiB

Raw Blame History

Connection Plugins

Connection plugins allow Ansible to connect to the target hosts so it can execute tasks on them. Ansible ships with many connection plugins, but only one can be used per host at a time.

By default, Ansible ships with several plugins. The most commonly used are the paramiko SSH<paramiko_ssh_connection>, native ssh (just called ssh<ssh_connection>), and local<local_connection> connection types. All of these can be used in playbooks and with /usr/bin/ansible to decide how you want to talk to remote machines.

The basics of these connection types are covered in the getting started<intro_getting_started> section.

`ssh` plugins

Because ssh is the default protocol used in system administration and the protocol most used in Ansible, ssh options are included in the command line tools. See ansible-playbook for more details.

Adding connection plugins

You can extend Ansible to support other transports (such as SNMP or message bus) by dropping a custom plugin into the connection_plugins directory.

Using connection plugins

You can set the connection plugin globally via configuration<ansible_configuration_settings>, at the command line (-c, --connection), as a keyword <playbook_keywords> in your play, or by setting a variable<behavioral_parameters>, most often in your inventory. For example, for Windows machines you might want to set the winrm <winrm_connection> plugin as an inventory variable.

Most connection plugins can operate with minimal configuration. By default they use the inventory hostname<inventory_hostnames_lookup> and defaults to find the target host.

Plugins are self-documenting. Each plugin should document its configuration options. The following are connection variables common to most connection plugins:

ansible_host<magic_variables_and_hostvars>: The name of the host to connect to, if different from the inventory <intro_inventory> hostname.
ansible_port<faq_setting_users_and_ports>: The ssh port number, for ssh <ssh_connection> and paramiko_ssh <paramiko_ssh_connection> it defaults to 22.
ansible_user<faq_setting_users_and_ports>: The default user name to use for log in. Most plugins default to the 'current user running Ansible'.

Each plugin might also have a specific version of a variable that overrides the general version. For example, ansible_ssh_host for the ssh <ssh_connection> plugin.

Plugin List

You can use ansible-doc -t connection -l to see the list of available plugins. Use ansible-doc -t connection <plugin name> to see detailed documentation and examples.

Working with Playbooks<working_with_playbooks>: An introduction to playbooks
callback_plugins: Ansible callback plugins
Filters<playbooks_filters>: Jinja2 filter plugins
Tests<playbooks_tests>: Jinja2 test plugins
Lookups<playbooks_lookups>: Jinja2 lookup plugins
vars_plugins: Ansible vars plugins
User Mailing List: Have a question? Stop by the google group!
irc.freenode.net: #ansible IRC chat channel

3.5 KiB Raw Blame History