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

Link to new network platform pages (#37057)

Browse source 
Also fix a few broken links
This commit is contained in:
John R Barker 2018-03-06 09:32:26 +00:00 committed by GitHub
parent 4ed0e5072d
commit 7a4e270ae0
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
2 changed files with 9 additions and 9 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

6
docs/docsite/rst/network/getting_started/network_differences.rst
View file

@ -30,7 +30,7 @@ Because network modules execute on the control node instead of on the managed no
"netconf", "XML over SSH", "network_os setting" "netconf", "XML over SSH", "network_os setting"
"local", "depends on provider", "provider setting" "local", "depends on provider", "provider setting"
Beginning with Ansible 2.5, we recommend using ``network_cli`` or ``netconf`` for ``ansible_connection`` whenever possible. For details on using API over HTTPS connections, see the platform-specific pages. Beginning with Ansible 2.5, we recommend using ``network_cli`` or ``netconf`` for ``ansible_connection`` whenever possible. For details on using API over HTTPS connections, see the :ref:`platform-specific <platform_options>` pages.
Modules Organized by Network Platform Modules Organized by Network Platform
@ -43,7 +43,7 @@ A network platform is a set of network devices with a common operating system th
- Juniper: ``junos_`` - Juniper: ``junos_``
- VyOS ``vyos_`` - VyOS ``vyos_``
All modules within a network platform share certain requirements. Some network platforms have specific differences - see the platform-specific documentation for details. All modules within a network platform share certain requirements. Some network platforms have specific differences - see the :ref:`platform-specific <platform_options>` documentation for details.
Privilege Escalation: `authorize` and `become` Privilege Escalation: `authorize` and `become`
@ -76,7 +76,7 @@ Some network platforms support privilege escalation but cannot use ``network_cli
transport: eapi transport: eapi
use_ssl: no use_ssl: no
And you use the ``setting`` variable in your play(s) or task(s): And you use the ``eapi`` variable in your play(s) or task(s):
.. code-block:: yaml .. code-block:: yaml

12
docs/docsite/rst/network/user_guide/network_best_practices_2.5.rst
View file

@ -22,10 +22,10 @@ Prerequisites
This example requires the following: This example requires the following:
* **Ansible 2.5** (or higher) installed. See :doc:`../installation_guide/intro_installation` for more information. * **Ansible 2.5** (or higher) installed. See :doc:`../../installation_guide/intro_installation` for more information.
* One or more network devices that are compatible with Ansible. * One or more network devices that are compatible with Ansible.
* Basic understanding of YAML :doc:`../reference_appendices/YAMLSyntax`. * Basic understanding of YAML :doc:`../../reference_appendices/YAMLSyntax`.
* Basic understanding of Jinja2 Templates. See :doc:`../user_guide/playbooks_templating` for more information. * Basic understanding of Jinja2 Templates. See :doc:`../../user_guide/playbooks_templating` for more information.
* Basic Linux command line use. * Basic Linux command line use.
* Basic knowledge of network switch & router configurations. * Basic knowledge of network switch & router configurations.
@ -118,7 +118,7 @@ Because Ansible is a flexible tool, there are a number of ways to specify connec
.. warning:: Never store passwords in plain text. .. warning:: Never store passwords in plain text.
The "Vault" feature of Ansible allows you to keep sensitive data such as passwords or keys in encrypted files, rather than as plain text in your playbooks or roles. These vault files can then be distributed or placed in source control. See :doc:`../user_guide/playbooks_vault` for more information. The "Vault" feature of Ansible allows you to keep sensitive data such as passwords or keys in encrypted files, rather than as plain text in your playbooks or roles. These vault files can then be distributed or placed in source control. See :doc:`../../user_guide/playbooks_vault` for more information.
:ansible_connection: :ansible_connection:
@ -361,8 +361,8 @@ If you receive an connection error please double check the inventory and Playboo
.. seealso:: .. seealso::
* :doc:`../network/index` * :ref:`network_guide`
* :doc:`../user_guide/intro_inventory` * :doc:`../../user_guide/intro_inventory`
* :ref:`Vault best practices <best_practices_for_variables_and_vaults>` * :ref:`Vault best practices <best_practices_for_variables_and_vaults>`