ansible/community.general
1
0
Fork 0
mirror of https://github.com/ansible-collections/community.general.git synced 2024-09-14 20:13:21 +02:00
Code Releases Activity

remove version detail from platform guides (#52512)

Browse source
This commit is contained in:
Sandra McCann 2019-02-19 11:04:07 -05:00 committed by Alicia Cozine
parent 63ea76d174
commit d7f5262dad
11 changed files with 39 additions and 39 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

12
docs/docsite/rst/network/user_guide/platform_eos.rst
View file

@ -4,7 +4,7 @@
EOS Platform Options
***************************************
Arista EOS supports multiple connections. This page offers details on how each connection works in Ansible 2.6 and how to use it.
Arista EOS supports multiple connections. This page offers details on how each connection works in Ansible and how to use it.
.. contents:: Topics
@ -41,8 +41,8 @@ Connections Available
For legacy playbooks, EOS still supports ``ansible_connection: local``. We recommend modernizing to use ``ansible_connection: network_cli`` or ``ansible_connection: httpapi`` as soon as possible.
Using CLI in Ansible 2.6
================================================================================
Using CLI in Ansible
====================
Example CLI ``group_vars/eos.yml``
----------------------------------
@ -76,8 +76,8 @@ Example CLI Task
Using eAPI in Ansible 2.6
================================================================================
Using eAPI in Ansible
=====================
Enabling eAPI
-------------
@ -161,7 +161,7 @@ eAPI task:
environment: "{{ proxy_env }}"
when: ansible_network_os == 'eos'
In this example two variables defined in ``group_vars`` get passed to the module of the task:
In this example two variables defined in ``group_vars`` get passed to the module of the task:
- the ``eapi`` variable gets passed to the ``provider`` option of the module
- the ``proxy_env`` variable gets passed to the ``environment`` option of the module

6
docs/docsite/rst/network/user_guide/platform_exos.rst
View file

@ -5,7 +5,7 @@ EXOS Platform Options
***************************************
Extreme EXOS Ansible modules only support CLI connections today. This page offers details on how to
use ``network_cli`` on EXOS in Ansible 2.6.
use ``network_cli`` on EXOS in Ansible.
.. contents:: Topics
@ -36,8 +36,8 @@ Connections Available
EXOS does not support ``ansible_connection: local``. You must use ``ansible_connection: network_cli``.
Using CLI in Ansible 2.6
================================================================================
Using CLI in Ansible
====================
Example CLI ``group_vars/exos.yml``
-----------------------------------

6
docs/docsite/rst/network/user_guide/platform_ios.rst
View file

@ -4,7 +4,7 @@
IOS Platform Options
***************************************
IOS supports Enable Mode (Privilege Escalation). This page offers details on how to use Enable Mode on IOS in Ansible 2.6.
IOS supports Enable Mode (Privilege Escalation). This page offers details on how to use Enable Mode on IOS in Ansible.
.. contents:: Topics
@ -34,8 +34,8 @@ Connections Available
For legacy playbooks, IOS still supports ``ansible_connection: local``. We recommend modernizing to use ``ansible_connection: network_cli`` as soon as possible.
Using CLI in Ansible 2.6
================================================================================
Using CLI in Ansible
====================
Example CLI ``group_vars/ios.yml``
----------------------------------

6
docs/docsite/rst/network/user_guide/platform_ironware.rst
View file

@ -4,7 +4,7 @@
IronWare Platform Options
***************************************
IronWare supports Enable Mode (Privilege Escalation). This page offers details on how to use Enable Mode on IronWare in Ansible 2.7.
IronWare supports Enable Mode (Privilege Escalation). This page offers details on how to use Enable Mode on IronWare in Ansible.
.. contents:: Topics
@ -34,8 +34,8 @@ Connections Available
For legacy playbooks, IronWare still supports ``ansible_connection: local``. We recommend modernizing to use ``ansible_connection: network_cli`` as soon as possible.
Using CLI in Ansible 2.6
================================================================================
Using CLI in Ansible
====================
Example CLI ``group_vars/mlx.yml``
----------------------------------

10
docs/docsite/rst/network/user_guide/platform_junos.rst
View file

@ -4,7 +4,7 @@
Junos OS Platform Options
***************************************
Juniper Junos OS supports multiple connections. This page offers details on how each connection works in Ansible 2.6 and how to use it.
Juniper Junos OS supports multiple connections. This page offers details on how each connection works in Ansible and how to use it.
.. contents:: Topics
@ -34,8 +34,8 @@ Connections Available
For legacy playbooks, Ansible still supports ``ansible_connection=local`` on all JUNOS modules. We recommend modernizing to use ``ansible_connection=netconf`` or ``ansible_connection=network_cli`` as soon as possible.
Using CLI in Ansible 2.6
================================================================================
Using CLI in Ansible
====================
Example CLI inventory ``[junos:vars]``
--------------------------------------
@ -65,8 +65,8 @@ Example CLI Task
when: ansible_network_os == 'junos'
Using NETCONF in Ansible 2.6
================================================================================
Using NETCONF in Ansible
========================
Enabling NETCONF
----------------

6
docs/docsite/rst/network/user_guide/platform_netconf_enabled.rst
View file

@ -4,7 +4,7 @@
Netconf enabled Platform Options
***************************************
This page offers details on how the netconf connection works in Ansible 2.7 and how to use it.
This page offers details on how the netconf connection works in Ansible and how to use it.
.. contents:: Topics
@ -27,8 +27,8 @@ Connections Available
For legacy playbooks, Ansible still supports ``ansible_connection=local`` for the netconf_config module only. We recommend modernizing to use ``ansible_connection=netconf`` as soon as possible.
Using NETCONF in Ansible 2.6 onwards
================================================================================
Using NETCONF in Ansible
========================
Enabling NETCONF
----------------

6
docs/docsite/rst/network/user_guide/platform_nos.rst
View file

@ -5,7 +5,7 @@ NOS Platform Options
***************************************
Extreme NOS Ansible modules only support CLI connections today. ``httpapi`` modules may be added in future.
This page offers details on how to use ``network_cli`` on NOS in Ansible >= 2.7.
This page offers details on how to use ``network_cli`` on NOS in Ansible.
.. contents:: Topics
@ -36,8 +36,8 @@ Connections Available
NOS does not support ``ansible_connection: local``. You must use ``ansible_connection: network_cli``.
Using CLI in Ansible >= 2.7
================================================================================
Using CLI in Ansible
====================
Example CLI ``group_vars/nos.yml``
----------------------------------

10
docs/docsite/rst/network/user_guide/platform_nxos.rst
View file

@ -4,7 +4,7 @@
NXOS Platform Options
***************************************
Cisco NXOS supports multiple connections. This page offers details on how each connection works in Ansible 2.6 and how to use it.
Cisco NXOS supports multiple connections. This page offers details on how each connection works in Ansible and how to use it.
.. contents:: Topics
@ -36,8 +36,8 @@ Connections Available
For legacy playbooks, NXOS still supports ``ansible_connection: local``. We recommend modernizing to use ``ansible_connection: network_cli`` or ``ansible_connection: httpapi`` as soon as possible.
Using CLI in Ansible 2.6
================================================================================
Using CLI in Ansible
====================
Example CLI ``group_vars/nxos.yml``
-----------------------------------
@ -71,8 +71,8 @@ Example CLI Task
Using NX-API in Ansible 2.6
================================================================================
Using NX-API in Ansible
=======================
Enabling NX-API
---------------

4
docs/docsite/rst/network/user_guide/platform_routeros.rst
View file

@ -29,8 +29,8 @@ Connections Available
| **Returned Data Format** | ``stdout[0].`` |
+---------------------------+-----------------------------------------------+
Using CLI in Ansible 2.6
================================================================================
Using CLI in Ansible
====================
Example CLI ``group_vars/routeros.yml``
---------------------------------------

6
docs/docsite/rst/network/user_guide/platform_slxos.rst
View file

@ -5,7 +5,7 @@ SLX-OS Platform Options
***************************************
Extreme SLX-OS Ansible modules only support CLI connections today. ``httpapi`` modules may be added in future.
This page offers details on how to use ``network_cli`` on SLX-OS in Ansible 2.6.
This page offers details on how to use ``network_cli`` on SLX-OS in Ansible.
.. contents:: Topics
@ -36,8 +36,8 @@ Connections Available
SLX-OS does not support ``ansible_connection: local``. You must use ``ansible_connection: network_cli``.
Using CLI in Ansible 2.6
================================================================================
Using CLI in Ansible
====================
Example CLI ``group_vars/slxos.yml``
------------------------------------

6
docs/docsite/rst/network/user_guide/platform_voss.rst
View file

@ -5,7 +5,7 @@ VOSS Platform Options
***************************************
Extreme VOSS Ansible modules only support CLI connections today. This page offers details on how to
use ``network_cli`` on VOSS in Ansible >= 2.7.
use ``network_cli`` on VOSS in Ansible.
.. contents:: Topics
@ -36,8 +36,8 @@ Connections Available
VOSS does not support ``ansible_connection: local``. You must use ``ansible_connection: network_cli``.
Using CLI in Ansible >= 2.7
================================================================================
Using CLI in Ansible
====================
Example CLI ``group_vars/voss.yml``
-----------------------------------