Files
offline_kubespray/collection/ansible/netcommon/docs/ansible.netcommon.httpapi_connection.rst
ByeonJungHun 360c6eef4a offline 작업
2024-02-19 16:02:29 +09:00

398 lines
18 KiB
ReStructuredText

.. _ansible.netcommon.httpapi_connection:
*************************
ansible.netcommon.httpapi
*************************
**Use httpapi to run command on network appliances**
Version added: 1.0.0
.. contents::
:local:
:depth: 1
Synopsis
--------
- This connection plugin provides a connection to remote devices over a HTTP(S)-based api.
Parameters
----------
.. raw:: html
<table border=0 cellpadding=0 class="documentation-table">
<tr>
<th colspan="1">Parameter</th>
<th>Choices/<font color="blue">Defaults</font></th>
<th>Configuration</th>
<th width="100%">Comments</th>
</tr>
<tr>
<td colspan="1">
<div class="ansibleOptionAnchor" id="parameter-"></div>
<b>become</b>
<a class="ansibleOptionLink" href="#parameter-" title="Permalink to this option"></a>
<div style="font-size: small">
<span style="color: purple">boolean</span>
</div>
</td>
<td>
<b>Default:</b><br/><div style="color: blue">"no"</div>
</td>
<td>
<div> ini entries:
<p>[privilege_escalation]<br>become = no</p>
</div>
<div>env:ANSIBLE_BECOME</div>
<div>var: ansible_become</div>
</td>
<td>
<div>The become option will instruct the CLI session to attempt privilege escalation on platforms that support it. Normally this means transitioning from user mode to <code>enable</code> mode in the CLI session. If become is set to True and the remote device does not support privilege escalation or the privilege has already been elevated, then this option is silently ignored.</div>
<div>Can be configured from the CLI via the <code>--become</code> or <code>-b</code> options.</div>
</td>
</tr>
<tr>
<td colspan="1">
<div class="ansibleOptionAnchor" id="parameter-"></div>
<b>become_method</b>
<a class="ansibleOptionLink" href="#parameter-" title="Permalink to this option"></a>
<div style="font-size: small">
<span style="color: purple">-</span>
</div>
</td>
<td>
<b>Default:</b><br/><div style="color: blue">"sudo"</div>
</td>
<td>
<div> ini entries:
<p>[privilege_escalation]<br>become_method = sudo</p>
</div>
<div>env:ANSIBLE_BECOME_METHOD</div>
<div>var: ansible_become_method</div>
</td>
<td>
<div>This option allows the become method to be specified in for handling privilege escalation. Typically the become_method value is set to <code>enable</code> but could be defined as other values.</div>
</td>
</tr>
<tr>
<td colspan="1">
<div class="ansibleOptionAnchor" id="parameter-"></div>
<b>host</b>
<a class="ansibleOptionLink" href="#parameter-" title="Permalink to this option"></a>
<div style="font-size: small">
<span style="color: purple">-</span>
</div>
</td>
<td>
<b>Default:</b><br/><div style="color: blue">"inventory_hostname"</div>
</td>
<td>
<div>var: ansible_host</div>
</td>
<td>
<div>Specifies the remote device FQDN or IP address to establish the HTTP(S) connection to.</div>
</td>
</tr>
<tr>
<td colspan="1">
<div class="ansibleOptionAnchor" id="parameter-"></div>
<b>import_modules</b>
<a class="ansibleOptionLink" href="#parameter-" title="Permalink to this option"></a>
<div style="font-size: small">
<span style="color: purple">boolean</span>
</div>
</td>
<td>
<b>Default:</b><br/><div style="color: blue">"no"</div>
</td>
<td>
<div> ini entries:
<p>[ansible_network]<br>import_modules = no</p>
</div>
<div>env:ANSIBLE_NETWORK_IMPORT_MODULES</div>
<div>var: ansible_network_import_modules</div>
</td>
<td>
<div>Reduce CPU usage and network module execution time by enabling direct execution. Instead of the module being packaged and executed by the shell, it will be directly executed by the Ansible control node using the same python interpreter as the Ansible process. Note- Incompatible with <code>asynchronous mode</code>. Note- Python 3 and Ansible 2.9.16 or greater required. Note- With Ansible 2.9.x fully qualified modules names are required in tasks.</div>
</td>
</tr>
<tr>
<td colspan="1">
<div class="ansibleOptionAnchor" id="parameter-"></div>
<b>network_os</b>
<a class="ansibleOptionLink" href="#parameter-" title="Permalink to this option"></a>
<div style="font-size: small">
<span style="color: purple">-</span>
</div>
</td>
<td>
</td>
<td>
<div>var: ansible_network_os</div>
</td>
<td>
<div>Configures the device platform network operating system. This value is used to load the correct httpapi plugin to communicate with the remote device</div>
</td>
</tr>
<tr>
<td colspan="1">
<div class="ansibleOptionAnchor" id="parameter-"></div>
<b>password</b>
<a class="ansibleOptionLink" href="#parameter-" title="Permalink to this option"></a>
<div style="font-size: small">
<span style="color: purple">-</span>
</div>
</td>
<td>
</td>
<td>
<div>var: ansible_password</div>
<div>var: ansible_httpapi_pass</div>
<div>var: ansible_httpapi_password</div>
</td>
<td>
<div>Configures the user password used to authenticate to the remote device when needed for the device API.</div>
</td>
</tr>
<tr>
<td colspan="1">
<div class="ansibleOptionAnchor" id="parameter-"></div>
<b>persistent_command_timeout</b>
<a class="ansibleOptionLink" href="#parameter-" title="Permalink to this option"></a>
<div style="font-size: small">
<span style="color: purple">integer</span>
</div>
</td>
<td>
<b>Default:</b><br/><div style="color: blue">30</div>
</td>
<td>
<div> ini entries:
<p>[persistent_connection]<br>command_timeout = 30</p>
</div>
<div>env:ANSIBLE_PERSISTENT_COMMAND_TIMEOUT</div>
<div>var: ansible_command_timeout</div>
</td>
<td>
<div>Configures, in seconds, the amount of time to wait for a command to return from the remote device. If this timer is exceeded before the command returns, the connection plugin will raise an exception and close.</div>
</td>
</tr>
<tr>
<td colspan="1">
<div class="ansibleOptionAnchor" id="parameter-"></div>
<b>persistent_connect_timeout</b>
<a class="ansibleOptionLink" href="#parameter-" title="Permalink to this option"></a>
<div style="font-size: small">
<span style="color: purple">integer</span>
</div>
</td>
<td>
<b>Default:</b><br/><div style="color: blue">30</div>
</td>
<td>
<div> ini entries:
<p>[persistent_connection]<br>connect_timeout = 30</p>
</div>
<div>env:ANSIBLE_PERSISTENT_CONNECT_TIMEOUT</div>
<div>var: ansible_connect_timeout</div>
</td>
<td>
<div>Configures, in seconds, the amount of time to wait when trying to initially establish a persistent connection. If this value expires before the connection to the remote device is completed, the connection will fail.</div>
</td>
</tr>
<tr>
<td colspan="1">
<div class="ansibleOptionAnchor" id="parameter-"></div>
<b>persistent_log_messages</b>
<a class="ansibleOptionLink" href="#parameter-" title="Permalink to this option"></a>
<div style="font-size: small">
<span style="color: purple">boolean</span>
</div>
</td>
<td>
<b>Default:</b><br/><div style="color: blue">"no"</div>
</td>
<td>
<div> ini entries:
<p>[persistent_connection]<br>log_messages = no</p>
</div>
<div>env:ANSIBLE_PERSISTENT_LOG_MESSAGES</div>
<div>var: ansible_persistent_log_messages</div>
</td>
<td>
<div>This flag will enable logging the command executed and response received from target device in the ansible log file. For this option to work &#x27;log_path&#x27; ansible configuration option is required to be set to a file path with write access.</div>
<div>Be sure to fully understand the security implications of enabling this option as it could create a security vulnerability by logging sensitive information in log file.</div>
</td>
</tr>
<tr>
<td colspan="1">
<div class="ansibleOptionAnchor" id="parameter-"></div>
<b>platform_type</b>
<a class="ansibleOptionLink" href="#parameter-" title="Permalink to this option"></a>
<div style="font-size: small">
<span style="color: purple">-</span>
</div>
</td>
<td>
</td>
<td>
<div>env:ANSIBLE_PLATFORM_TYPE</div>
<div>var: ansible_platform_type</div>
</td>
<td>
<div>Set type of platform.</div>
</td>
</tr>
<tr>
<td colspan="1">
<div class="ansibleOptionAnchor" id="parameter-"></div>
<b>port</b>
<a class="ansibleOptionLink" href="#parameter-" title="Permalink to this option"></a>
<div style="font-size: small">
<span style="color: purple">integer</span>
</div>
</td>
<td>
</td>
<td>
<div> ini entries:
<p>[defaults]<br>remote_port = VALUE</p>
</div>
<div>env:ANSIBLE_REMOTE_PORT</div>
<div>var: ansible_httpapi_port</div>
</td>
<td>
<div>Specifies the port on the remote device that listens for connections when establishing the HTTP(S) connection.</div>
<div>When unspecified, will pick 80 or 443 based on the value of use_ssl.</div>
</td>
</tr>
<tr>
<td colspan="1">
<div class="ansibleOptionAnchor" id="parameter-"></div>
<b>remote_user</b>
<a class="ansibleOptionLink" href="#parameter-" title="Permalink to this option"></a>
<div style="font-size: small">
<span style="color: purple">-</span>
</div>
</td>
<td>
</td>
<td>
<div> ini entries:
<p>[defaults]<br>remote_user = VALUE</p>
</div>
<div>env:ANSIBLE_REMOTE_USER</div>
<div>var: ansible_user</div>
</td>
<td>
<div>The username used to authenticate to the remote device when the API connection is first established. If the remote_user is not specified, the connection will use the username of the logged in user.</div>
<div>Can be configured from the CLI via the <code>--user</code> or <code>-u</code> options.</div>
</td>
</tr>
<tr>
<td colspan="1">
<div class="ansibleOptionAnchor" id="parameter-"></div>
<b>session_key</b>
<a class="ansibleOptionLink" href="#parameter-" title="Permalink to this option"></a>
<div style="font-size: small">
<span style="color: purple">dictionary</span>
</div>
</td>
<td>
</td>
<td>
<div>var: ansible_httpapi_session_key</div>
</td>
<td>
<div>Configures the session key to be used to authenticate to the remote device when needed for the device API.</div>
<div>This should contain a dictionary representing the key name and value for the token.</div>
<div>When specified, <em>password</em> is ignored.</div>
</td>
</tr>
<tr>
<td colspan="1">
<div class="ansibleOptionAnchor" id="parameter-"></div>
<b>use_proxy</b>
<a class="ansibleOptionLink" href="#parameter-" title="Permalink to this option"></a>
<div style="font-size: small">
<span style="color: purple">boolean</span>
</div>
</td>
<td>
<b>Default:</b><br/><div style="color: blue">"yes"</div>
</td>
<td>
<div>var: ansible_httpapi_use_proxy</div>
</td>
<td>
<div>Whether to use https_proxy for requests.</div>
</td>
</tr>
<tr>
<td colspan="1">
<div class="ansibleOptionAnchor" id="parameter-"></div>
<b>use_ssl</b>
<a class="ansibleOptionLink" href="#parameter-" title="Permalink to this option"></a>
<div style="font-size: small">
<span style="color: purple">boolean</span>
</div>
</td>
<td>
<b>Default:</b><br/><div style="color: blue">"no"</div>
</td>
<td>
<div>var: ansible_httpapi_use_ssl</div>
</td>
<td>
<div>Whether to connect using SSL (HTTPS) or not (HTTP).</div>
</td>
</tr>
<tr>
<td colspan="1">
<div class="ansibleOptionAnchor" id="parameter-"></div>
<b>validate_certs</b>
<a class="ansibleOptionLink" href="#parameter-" title="Permalink to this option"></a>
<div style="font-size: small">
<span style="color: purple">boolean</span>
</div>
</td>
<td>
<b>Default:</b><br/><div style="color: blue">"yes"</div>
</td>
<td>
<div>var: ansible_httpapi_validate_certs</div>
</td>
<td>
<div>Whether to validate SSL certificates</div>
</td>
</tr>
</table>
<br/>
Status
------
Authors
~~~~~~~
- Ansible Networking Team (@ansible-network)
.. hint::
Configuration entries for each entry type have a low to high priority order. For example, a variable that is lower in the list will override a variable that is higher up.