From c0901fcba55d7d5d935932f07ee480ca889df874 Mon Sep 17 00:00:00 2001 From: Sandra McCann Date: Thu, 6 Oct 2022 18:00:18 -0400 Subject: [PATCH] Fixed Latin words, replaced all via with either through or by (#79004) (#79068) (cherry picked from commit 4f4ad453c4c304c46901931bd9570e8213abb560) Co-authored-by: Ishan Siddiqui <77967215+ishan-siddiqui@users.noreply.github.com> --- docs/docsite/rst/network/user_guide/platform_cnos.rst | 4 ++-- docs/docsite/rst/network/user_guide/platform_dellos10.rst | 4 ++-- docs/docsite/rst/network/user_guide/platform_dellos6.rst | 4 ++-- docs/docsite/rst/network/user_guide/platform_dellos9.rst | 4 ++-- docs/docsite/rst/network/user_guide/platform_enos.rst | 4 ++-- docs/docsite/rst/network/user_guide/platform_eos.rst | 4 ++-- docs/docsite/rst/network/user_guide/platform_eric_eccli.rst | 4 ++-- docs/docsite/rst/network/user_guide/platform_exos.rst | 4 ++-- docs/docsite/rst/network/user_guide/platform_frr.rst | 4 ++-- docs/docsite/rst/network/user_guide/platform_icx.rst | 4 ++-- docs/docsite/rst/network/user_guide/platform_ios.rst | 4 ++-- docs/docsite/rst/network/user_guide/platform_iosxr.rst | 4 ++-- docs/docsite/rst/network/user_guide/platform_ironware.rst | 4 ++-- docs/docsite/rst/network/user_guide/platform_junos.rst | 6 +++--- .../rst/network/user_guide/platform_netconf_enabled.rst | 4 ++-- docs/docsite/rst/network/user_guide/platform_netvisor.rst | 4 ++-- docs/docsite/rst/network/user_guide/platform_nos.rst | 4 ++-- docs/docsite/rst/network/user_guide/platform_nxos.rst | 6 +++--- docs/docsite/rst/network/user_guide/platform_routeros.rst | 4 ++-- docs/docsite/rst/network/user_guide/platform_slxos.rst | 4 ++-- docs/docsite/rst/network/user_guide/platform_voss.rst | 4 ++-- docs/docsite/rst/network/user_guide/platform_vyos.rst | 4 ++-- docs/docsite/rst/network/user_guide/platform_weos4.rst | 4 ++-- 23 files changed, 48 insertions(+), 48 deletions(-) diff --git a/docs/docsite/rst/network/user_guide/platform_cnos.rst b/docs/docsite/rst/network/user_guide/platform_cnos.rst index 62e1d54993a..00448474072 100644 --- a/docs/docsite/rst/network/user_guide/platform_cnos.rst +++ b/docs/docsite/rst/network/user_guide/platform_cnos.rst @@ -24,7 +24,7 @@ Connections available accepts ``-u myuser -k`` if using password - Indirect Access via a bastion (jump host) + Indirect Access by a bastion (jump host) Connection Settings ``ansible_connection: ansible.netcommon.network_cli`` @@ -59,7 +59,7 @@ Example CLI ``group_vars/cnos.yml`` - If you are using SSH keys (including an ssh-agent) you can remove the ``ansible_password`` configuration. - If you are accessing your host directly (not through a bastion/jump host) you can remove the ``ansible_ssh_common_args`` configuration. -- If you are accessing your host through a bastion/jump host, you cannot include your SSH password in the ``ProxyCommand`` directive. To prevent secrets from leaking out (for example in ``ps`` output), SSH does not support providing passwords via environment variables. +- If you are accessing your host through a bastion/jump host, you cannot include your SSH password in the ``ProxyCommand`` directive. To prevent secrets from leaking out (for example in ``ps`` output), SSH does not support providing passwords through environment variables. Example CLI task ---------------- diff --git a/docs/docsite/rst/network/user_guide/platform_dellos10.rst b/docs/docsite/rst/network/user_guide/platform_dellos10.rst index 638932a275d..cdffdd5545a 100644 --- a/docs/docsite/rst/network/user_guide/platform_dellos10.rst +++ b/docs/docsite/rst/network/user_guide/platform_dellos10.rst @@ -24,7 +24,7 @@ Connections available accepts ``-u myuser -k`` if using password - Indirect Access via a bastion (jump host) + Indirect Access through a bastion (jump host) Connection Settings ``ansible_connection: ansible.netcommon.network_cli`` @@ -60,7 +60,7 @@ Example CLI ``group_vars/dellos10.yml`` - If you are using SSH keys (including an ssh-agent) you can remove the ``ansible_password`` configuration. - If you are accessing your host directly (not through a bastion/jump host) you can remove the ``ansible_ssh_common_args`` configuration. -- If you are accessing your host through a bastion/jump host, you cannot include your SSH password in the ``ProxyCommand`` directive. To prevent secrets from leaking out (for example in ``ps`` output), SSH does not support providing passwords via environment variables. +- If you are accessing your host through a bastion/jump host, you cannot include your SSH password in the ``ProxyCommand`` directive. To prevent secrets from leaking out (for example in ``ps`` output), SSH does not support providing passwords through environment variables. Example CLI task ---------------- diff --git a/docs/docsite/rst/network/user_guide/platform_dellos6.rst b/docs/docsite/rst/network/user_guide/platform_dellos6.rst index d315c59d93d..ae8083de8d9 100644 --- a/docs/docsite/rst/network/user_guide/platform_dellos6.rst +++ b/docs/docsite/rst/network/user_guide/platform_dellos6.rst @@ -24,7 +24,7 @@ Connections available accepts ``-u myuser -k`` if using password - Indirect Access via a bastion (jump host) + Indirect Access through a bastion (jump host) Connection Settings ``ansible_connection: ansible.netcommon.network_cli`` @@ -59,7 +59,7 @@ Example CLI ``group_vars/dellos6.yml`` - If you are using SSH keys (including an ssh-agent) you can remove the ``ansible_password`` configuration. - If you are accessing your host directly (not through a bastion/jump host) you can remove the ``ansible_ssh_common_args`` configuration. -- If you are accessing your host through a bastion/jump host, you cannot include your SSH password in the ``ProxyCommand`` directive. To prevent secrets from leaking out (for example in ``ps`` output), SSH does not support providing passwords via environment variables. +- If you are accessing your host through a bastion/jump host, you cannot include your SSH password in the ``ProxyCommand`` directive. To prevent secrets from leaking out (for example in ``ps`` output), SSH does not support providing passwords through environment variables. Example CLI task ---------------- diff --git a/docs/docsite/rst/network/user_guide/platform_dellos9.rst b/docs/docsite/rst/network/user_guide/platform_dellos9.rst index cadde62284d..ac1f52f63db 100644 --- a/docs/docsite/rst/network/user_guide/platform_dellos9.rst +++ b/docs/docsite/rst/network/user_guide/platform_dellos9.rst @@ -24,7 +24,7 @@ Connections available accepts ``-u myuser -k`` if using password - Indirect Access via a bastion (jump host) + Indirect Access through a bastion (jump host) Connection Settings ``ansible_connection: ansible.netcommon.network_cli`` @@ -59,7 +59,7 @@ Example CLI ``group_vars/dellos9.yml`` - If you are using SSH keys (including an ssh-agent) you can remove the ``ansible_password`` configuration. - If you are accessing your host directly (not through a bastion/jump host) you can remove the ``ansible_ssh_common_args`` configuration. -- If you are accessing your host through a bastion/jump host, you cannot include your SSH password in the ``ProxyCommand`` directive. To prevent secrets from leaking out (for example in ``ps`` output), SSH does not support providing passwords via environment variables. +- If you are accessing your host through a bastion/jump host, you cannot include your SSH password in the ``ProxyCommand`` directive. To prevent secrets from leaking out (for example in ``ps`` output), SSH does not support providing passwords through environment variables. Example CLI task ---------------- diff --git a/docs/docsite/rst/network/user_guide/platform_enos.rst b/docs/docsite/rst/network/user_guide/platform_enos.rst index 58c0b83e057..3cf17c30eee 100644 --- a/docs/docsite/rst/network/user_guide/platform_enos.rst +++ b/docs/docsite/rst/network/user_guide/platform_enos.rst @@ -24,7 +24,7 @@ Connections available accepts ``-u myuser -k`` if using password - Indirect Access via a bastion (jump host) + Indirect Access by a bastion (jump host) Connection Settings ``ansible_connection: ansible.netcommon.network_cli`` @@ -61,7 +61,7 @@ Example CLI ``group_vars/enos.yml`` - If you are using SSH keys (including an ssh-agent) you can remove the ``ansible_password`` configuration. - If you are accessing your host directly (not through a bastion/jump host) you can remove the ``ansible_ssh_common_args`` configuration. -- If you are accessing your host through a bastion/jump host, you cannot include your SSH password in the ``ProxyCommand`` directive. To prevent secrets from leaking out (for example in ``ps`` output), SSH does not support providing passwords via environment variables. +- If you are accessing your host through a bastion/jump host, you cannot include your SSH password in the ``ProxyCommand`` directive. To prevent secrets from leaking out (for example in ``ps`` output), SSH does not support providing passwords through environment variables. Example CLI task ---------------- diff --git a/docs/docsite/rst/network/user_guide/platform_eos.rst b/docs/docsite/rst/network/user_guide/platform_eos.rst index 065a7dc0627..588118ef27c 100644 --- a/docs/docsite/rst/network/user_guide/platform_eos.rst +++ b/docs/docsite/rst/network/user_guide/platform_eos.rst @@ -24,7 +24,7 @@ Connections available present accepts ``-u myuser -k`` if using password - Indirect Access via a bastion (jump host) via a web proxy + Indirect Access by a bastion (jump host) through a web proxy Connection Settings ``ansible_connection:`` ``ansible_connection:`` ``ansible.netcommon.network_cli`` ``ansible.netcommon.httpapi`` @@ -64,7 +64,7 @@ Example CLI ``group_vars/eos.yml`` - If you are using SSH keys (including an ssh-agent) you can remove the ``ansible_password`` configuration. - If you are accessing your host directly (not through a bastion/jump host) you can remove the ``ansible_ssh_common_args`` configuration. -- If you are accessing your host through a bastion/jump host, you cannot include your SSH password in the ``ProxyCommand`` directive. To prevent secrets from leaking out (for example in ``ps`` output), SSH does not support providing passwords via environment variables. +- If you are accessing your host through a bastion/jump host, you cannot include your SSH password in the ``ProxyCommand`` directive. To prevent secrets from leaking out (for example in ``ps`` output), SSH does not support providing passwords through environment variables. Example CLI task ---------------- diff --git a/docs/docsite/rst/network/user_guide/platform_eric_eccli.rst b/docs/docsite/rst/network/user_guide/platform_eric_eccli.rst index cdd45779e01..8e8bef0178c 100644 --- a/docs/docsite/rst/network/user_guide/platform_eric_eccli.rst +++ b/docs/docsite/rst/network/user_guide/platform_eric_eccli.rst @@ -24,7 +24,7 @@ Connections available accepts ``-u myuser -k`` if using password - Indirect Access via a bastion (jump host) + Indirect Access by a bastion (jump host) Connection Settings ``ansible_connection: ansible.netcommon.network_cli`` @@ -54,7 +54,7 @@ Example CLI ``group_vars/eric_eccli.yml`` - If you are using SSH keys (including an ssh-agent) you can remove the ``ansible_password`` configuration. - If you are accessing your host directly (not through a bastion/jump host) you can remove the ``ansible_ssh_common_args`` configuration. -- If you are accessing your host through a bastion/jump host, you cannot include your SSH password in the ``ProxyCommand`` directive. To prevent secrets from leaking out (for example in ``ps`` output), SSH does not support providing passwords via environment variables. +- If you are accessing your host through a bastion/jump host, you cannot include your SSH password in the ``ProxyCommand`` directive. To prevent secrets from leaking out (for example in ``ps`` output), SSH does not support providing passwords through environment variables. Example CLI task ---------------- diff --git a/docs/docsite/rst/network/user_guide/platform_exos.rst b/docs/docsite/rst/network/user_guide/platform_exos.rst index e27e9ae4bcf..2e74be53f33 100644 --- a/docs/docsite/rst/network/user_guide/platform_exos.rst +++ b/docs/docsite/rst/network/user_guide/platform_exos.rst @@ -25,7 +25,7 @@ Connections available accepts ``-u myuser -k`` if using password - Indirect Access via a bastion (jump host) via a web proxy + Indirect Access by a bastion (jump host) through a web proxy Connection Settings ``ansible_connection:`` ``ansible_connection:`` ``ansible.netcommon.network_cli`` ``ansible.netcommon.httpapi`` @@ -56,7 +56,7 @@ Example CLI ``group_vars/exos.yml`` - If you are using SSH keys (including an ssh-agent) you can remove the ``ansible_password`` configuration. - If you are accessing your host directly (not through a bastion/jump host) you can remove the ``ansible_ssh_common_args`` configuration. -- If you are accessing your host through a bastion/jump host, you cannot include your SSH password in the ``ProxyCommand`` directive. To prevent secrets from leaking out (for example in ``ps`` output), SSH does not support providing passwords via environment variables. +- If you are accessing your host through a bastion/jump host, you cannot include your SSH password in the ``ProxyCommand`` directive. To prevent secrets from leaking out (for example in ``ps`` output), SSH does not support providing passwords through environment variables. Example CLI task ---------------- diff --git a/docs/docsite/rst/network/user_guide/platform_frr.rst b/docs/docsite/rst/network/user_guide/platform_frr.rst index 0d7bad14c03..026125098c5 100644 --- a/docs/docsite/rst/network/user_guide/platform_frr.rst +++ b/docs/docsite/rst/network/user_guide/platform_frr.rst @@ -24,7 +24,7 @@ Connections available accepts ``-u myuser -k`` if using password - Indirect Access via a bastion (jump host) + Indirect Access by a bastion (jump host) Connection Settings ``ansible_connection: ansible.netcommon.network_cli`` @@ -53,7 +53,7 @@ Example CLI ``group_vars/frr.yml`` - The ``ansible_user`` should be a part of the ``frrvty`` group and should have the default shell set to ``/bin/vtysh``. - If you are using SSH keys (including an ssh-agent) you can remove the ``ansible_password`` configuration. - If you are accessing your host directly (not through a bastion/jump host) you can remove the ``ansible_ssh_common_args`` configuration. -- If you are accessing your host through a bastion/jump host, you cannot include your SSH password in the ``ProxyCommand`` directive. To prevent secrets from leaking out (for example in ``ps`` output), SSH does not support providing passwords via environment variables. +- If you are accessing your host through a bastion/jump host, you cannot include your SSH password in the ``ProxyCommand`` directive. To prevent secrets from leaking out (for example in ``ps`` output), SSH does not support providing passwords through environment variables. Example CLI task ---------------- diff --git a/docs/docsite/rst/network/user_guide/platform_icx.rst b/docs/docsite/rst/network/user_guide/platform_icx.rst index 96777f1ec60..ee87b7682bf 100644 --- a/docs/docsite/rst/network/user_guide/platform_icx.rst +++ b/docs/docsite/rst/network/user_guide/platform_icx.rst @@ -24,7 +24,7 @@ Connections available accepts ``-u myuser -k`` if using password - Indirect Access via a bastion (jump host) + Indirect Access by a bastion (jump host) Connection Settings ``ansible_connection: ansible.netcommon.network_cli`` @@ -57,7 +57,7 @@ Example CLI ``group_vars/icx.yml`` - If you are using SSH keys (including an ssh-agent) you can remove the ``ansible_password`` configuration. - If you are accessing your host directly (not through a bastion/jump host) you can remove the ``ansible_ssh_common_args`` configuration. -- If you are accessing your host through a bastion/jump host, you cannot include your SSH password in the ``ProxyCommand`` directive. To prevent secrets from leaking out (for example in ``ps`` output), SSH does not support providing passwords via environment variables. +- If you are accessing your host through a bastion/jump host, you cannot include your SSH password in the ``ProxyCommand`` directive. To prevent secrets from leaking out (for example in ``ps`` output), SSH does not support providing passwords through environment variables. Example CLI task ---------------- diff --git a/docs/docsite/rst/network/user_guide/platform_ios.rst b/docs/docsite/rst/network/user_guide/platform_ios.rst index 1c53a5ca013..c7bd9ab768b 100644 --- a/docs/docsite/rst/network/user_guide/platform_ios.rst +++ b/docs/docsite/rst/network/user_guide/platform_ios.rst @@ -24,7 +24,7 @@ Connections available accepts ``-u myuser -k`` if using password - Indirect Access via a bastion (jump host) + Indirect Access by a bastion (jump host) Connection Settings ``ansible_connection: ansible.netcommon.network_cli`` @@ -59,7 +59,7 @@ Example CLI ``group_vars/ios.yml`` - If you are using SSH keys (including an ssh-agent) you can remove the ``ansible_password`` configuration. - If you are accessing your host directly (not through a bastion/jump host) you can remove the ``ansible_ssh_common_args`` configuration. -- If you are accessing your host through a bastion/jump host, you cannot include your SSH password in the ``ProxyCommand`` directive. To prevent secrets from leaking out (for example in ``ps`` output), SSH does not support providing passwords via environment variables. +- If you are accessing your host through a bastion/jump host, you cannot include your SSH password in the ``ProxyCommand`` directive. To prevent secrets from leaking out (for example in ``ps`` output), SSH does not support providing passwords through environment variables. Example CLI task ---------------- diff --git a/docs/docsite/rst/network/user_guide/platform_iosxr.rst b/docs/docsite/rst/network/user_guide/platform_iosxr.rst index 1e1eab27a51..30e49951c3c 100644 --- a/docs/docsite/rst/network/user_guide/platform_iosxr.rst +++ b/docs/docsite/rst/network/user_guide/platform_iosxr.rst @@ -28,7 +28,7 @@ Connections available accepts ``-u myuser -k`` if using password accepts ``-u myuser -k`` if using password - Indirect Access via a bastion (jump host) via a bastion (jump host) + Indirect Access by a bastion (jump host) by a bastion (jump host) Connection Settings ``ansible_connection:`` ``ansible_connection:`` ``ansible.netcommon.network_cli`` ``ansible.netcommon.netconf`` @@ -61,7 +61,7 @@ Example CLI inventory ``[iosxr:vars]`` - If you are using SSH keys (including an ssh-agent) you can remove the ``ansible_password`` configuration. - If you are accessing your host directly (not through a bastion/jump host) you can remove the ``ansible_ssh_common_args`` configuration. -- If you are accessing your host through a bastion/jump host, you cannot include your SSH password in the ``ProxyCommand`` directive. To prevent secrets from leaking out (for example in ``ps`` output), SSH does not support providing passwords via environment variables. +- If you are accessing your host through a bastion/jump host, you cannot include your SSH password in the ``ProxyCommand`` directive. To prevent secrets from leaking out (for example in ``ps`` output), SSH does not support providing passwords through environment variables. Example CLI task ---------------- diff --git a/docs/docsite/rst/network/user_guide/platform_ironware.rst b/docs/docsite/rst/network/user_guide/platform_ironware.rst index a17141c4cdc..dbb2c412269 100644 --- a/docs/docsite/rst/network/user_guide/platform_ironware.rst +++ b/docs/docsite/rst/network/user_guide/platform_ironware.rst @@ -24,7 +24,7 @@ Connections available accepts ``-u myuser -k`` if using password - Indirect Access via a bastion (jump host) + Indirect Access by a bastion (jump host) Connection Settings ``ansible_connection: ansible.netcommon.network_cli`` @@ -60,7 +60,7 @@ Example CLI ``group_vars/mlx.yml`` - If you are using SSH keys (including an ssh-agent) you can remove the ``ansible_password`` configuration. - If you are accessing your host directly (not through a bastion/jump host) you can remove the ``ansible_ssh_common_args`` configuration. -- If you are accessing your host through a bastion/jump host, you cannot include your SSH password in the ``ProxyCommand`` directive. To prevent secrets from leaking out (for example in ``ps`` output), SSH does not support providing passwords via environment variables. +- If you are accessing your host through a bastion/jump host, you cannot include your SSH password in the ``ProxyCommand`` directive. To prevent secrets from leaking out (for example in ``ps`` output), SSH does not support providing passwords through environment variables. Example CLI task ---------------- diff --git a/docs/docsite/rst/network/user_guide/platform_junos.rst b/docs/docsite/rst/network/user_guide/platform_junos.rst index 3b83810344b..08cf8fc0d11 100644 --- a/docs/docsite/rst/network/user_guide/platform_junos.rst +++ b/docs/docsite/rst/network/user_guide/platform_junos.rst @@ -27,7 +27,7 @@ Connections available accepts ``-u myuser -k`` if using password accepts ``-u myuser -k`` if using password - Indirect Access via a bastion (jump host) via a bastion (jump host) + Indirect Access by a bastion (jump host) by a bastion (jump host) Connection Settings ``ansible_connection: ``ansible_connection: ``ansible.netcommon.network_cli`` ``ansible.netcommon.netconf`` @@ -62,7 +62,7 @@ Example CLI inventory ``[junos:vars]`` - If you are using SSH keys (including an ssh-agent) you can remove the ``ansible_password`` configuration. - If you are accessing your host directly (not through a bastion/jump host) you can remove the ``ansible_ssh_common_args`` configuration. -- If you are accessing your host through a bastion/jump host, you cannot include your SSH password in the ``ProxyCommand`` directive. To prevent secrets from leaking out (for example in ``ps`` output), SSH does not support providing passwords via environment variables. +- If you are accessing your host through a bastion/jump host, you cannot include your SSH password in the ``ProxyCommand`` directive. To prevent secrets from leaking out (for example in ``ps`` output), SSH does not support providing passwords through environment variables. Example CLI task ---------------- @@ -86,7 +86,7 @@ Before you can use NETCONF to connect to a switch, you must: - install the ``ncclient`` python package on your control node(s) with ``pip install ncclient`` - enable NETCONF on the Junos OS device(s) -To enable NETCONF on a new switch via Ansible, use the ``junipernetworks.junos.junos_netconf`` module through the CLI connection. Set up your platform-level variables just like in the CLI example above, then run a playbook task like this: +To enable NETCONF on a new switch through Ansible, use the ``junipernetworks.junos.junos_netconf`` module through the CLI connection. Set up your platform-level variables just like in the CLI example above, then run a playbook task like this: .. code-block:: yaml diff --git a/docs/docsite/rst/network/user_guide/platform_netconf_enabled.rst b/docs/docsite/rst/network/user_guide/platform_netconf_enabled.rst index 6169b076096..e481ed62735 100644 --- a/docs/docsite/rst/network/user_guide/platform_netconf_enabled.rst +++ b/docs/docsite/rst/network/user_guide/platform_netconf_enabled.rst @@ -26,7 +26,7 @@ Connections available accepts ``-u myuser -k`` if using password - Indirect Access via a bastion (jump host) + Indirect Access through a bastion (jump host) Connection Settings ``ansible_connection: ansible.netcommon.netconf`` ==================== ========================================== @@ -45,7 +45,7 @@ Before you can use NETCONF to connect to a switch, you must: - install the ``ncclient`` Python package on your control node(s) with ``pip install ncclient`` - enable NETCONF on the Junos OS device(s) -To enable NETCONF on a new switch via Ansible, use the platform specific module via the CLI connection or set it manually. +To enable NETCONF on a new switch through Ansible, use the platform specific module through the CLI connection or set it manually. For example set up your platform-level variables just like in the CLI example above, then run a playbook task like this: .. code-block:: yaml diff --git a/docs/docsite/rst/network/user_guide/platform_netvisor.rst b/docs/docsite/rst/network/user_guide/platform_netvisor.rst index 57748658a71..648e9c1cad6 100644 --- a/docs/docsite/rst/network/user_guide/platform_netvisor.rst +++ b/docs/docsite/rst/network/user_guide/platform_netvisor.rst @@ -25,7 +25,7 @@ Connections available accepts ``-u myuser -k`` if using password - Indirect Access via a bastion (jump host) + Indirect Access by a bastion (jump host) Connection Settings ``ansible_connection: ansible.netcommon.network_cli`` @@ -55,7 +55,7 @@ Example CLI ``group_vars/netvisor.yml`` - If you are using SSH keys (including an ssh-agent) you can remove the ``ansible_password`` configuration. - If you are accessing your host directly (not through a bastion/jump host) you can remove the ``ansible_ssh_common_args`` configuration. -- If you are accessing your host through a bastion/jump host, you cannot include your SSH password in the ``ProxyCommand`` directive. To prevent secrets from leaking out (for example in ``ps`` output), SSH does not support providing passwords via environment variables. +- If you are accessing your host through a bastion/jump host, you cannot include your SSH password in the ``ProxyCommand`` directive. To prevent secrets from leaking out (for example in ``ps`` output), SSH does not support providing passwords through environment variables. Example CLI task ---------------- diff --git a/docs/docsite/rst/network/user_guide/platform_nos.rst b/docs/docsite/rst/network/user_guide/platform_nos.rst index 0ea3f529fbe..6bc244c8d9b 100644 --- a/docs/docsite/rst/network/user_guide/platform_nos.rst +++ b/docs/docsite/rst/network/user_guide/platform_nos.rst @@ -25,7 +25,7 @@ Connections available accepts ``-u myuser -k`` if using password - Indirect Access via a bastion (jump host) + Indirect Access by a bastion (jump host) Connection Settings ``ansible_connection: community.netcommon.network_cli`` @@ -55,7 +55,7 @@ Example CLI ``group_vars/nos.yml`` - If you are using SSH keys (including an ssh-agent) you can remove the ``ansible_password`` configuration. - If you are accessing your host directly (not through a bastion/jump host) you can remove the ``ansible_ssh_common_args`` configuration. -- If you are accessing your host through a bastion/jump host, you cannot include your SSH password in the ``ProxyCommand`` directive. To prevent secrets from leaking out (for example in ``ps`` output), SSH does not support providing passwords via environment variables. +- If you are accessing your host through a bastion/jump host, you cannot include your SSH password in the ``ProxyCommand`` directive. To prevent secrets from leaking out (for example in ``ps`` output), SSH does not support providing passwords through environment variables. Example CLI task ---------------- diff --git a/docs/docsite/rst/network/user_guide/platform_nxos.rst b/docs/docsite/rst/network/user_guide/platform_nxos.rst index 70ee78bdadd..3794cfc3313 100644 --- a/docs/docsite/rst/network/user_guide/platform_nxos.rst +++ b/docs/docsite/rst/network/user_guide/platform_nxos.rst @@ -24,7 +24,7 @@ Connections available present accepts ``-u myuser -k`` if using password - Indirect Access via a bastion (jump host) via a web proxy + Indirect Access by a bastion (jump host) by a web proxy Connection Settings ``ansible_connection:`` ``ansible_connection:`` ``ansible.netcommon.network_cli`` ``ansible.netcommon.httpapi`` @@ -61,7 +61,7 @@ Example CLI ``group_vars/nxos.yml`` - If you are using SSH keys (including an ssh-agent) you can remove the ``ansible_password`` configuration. - If you are accessing your host directly (not through a bastion/jump host) you can remove the ``ansible_ssh_common_args`` configuration. -- If you are accessing your host through a bastion/jump host, you cannot include your SSH password in the ``ProxyCommand`` directive. To prevent secrets from leaking out (for example in ``ps`` output), SSH does not support providing passwords via environment variables. +- If you are accessing your host through a bastion/jump host, you cannot include your SSH password in the ``ProxyCommand`` directive. To prevent secrets from leaking out (for example in ``ps`` output), SSH does not support providing passwords through environment variables. Example CLI task ---------------- @@ -82,7 +82,7 @@ Using NX-API in Ansible Enabling NX-API --------------- -Before you can use NX-API to connect to a switch, you must enable NX-API. To enable NX-API on a new switch via Ansible, use the ``nxos_nxapi`` module via the CLI connection. Set up group_vars/nxos.yml just like in the CLI example above, then run a playbook task like this: +Before you can use NX-API to connect to a switch, you must enable NX-API. To enable NX-API on a new switch through Ansible, use the ``nxos_nxapi`` module through the CLI connection. Set up group_vars/nxos.yml just like in the CLI example above, then run a playbook task like this: .. code-block:: yaml diff --git a/docs/docsite/rst/network/user_guide/platform_routeros.rst b/docs/docsite/rst/network/user_guide/platform_routeros.rst index 387db92d7d2..ff404e6672d 100644 --- a/docs/docsite/rst/network/user_guide/platform_routeros.rst +++ b/docs/docsite/rst/network/user_guide/platform_routeros.rst @@ -25,7 +25,7 @@ Connections available accepts ``-u myuser -k`` if using password - Indirect Access via a bastion (jump host) + Indirect Access by a bastion (jump host) Connection Settings ``ansible_connection: ansible.network.network_cli`` @@ -59,7 +59,7 @@ Example CLI ``group_vars/routeros.yml`` - If you are using SSH keys (including an ssh-agent) you can remove the ``ansible_password`` configuration. - If you are accessing your host directly (not through a bastion/jump host) you can remove the ``ansible_ssh_common_args`` configuration. -- If you are accessing your host through a bastion/jump host, you cannot include your SSH password in the ``ProxyCommand`` directive. To prevent secrets from leaking out (for example in ``ps`` output), SSH does not support providing passwords via environment variables. +- If you are accessing your host through a bastion/jump host, you cannot include your SSH password in the ``ProxyCommand`` directive. To prevent secrets from leaking out (for example in ``ps`` output), SSH does not support providing passwords through environment variables. - If you are getting timeout errors you may want to add ``+cet1024w`` suffix to your username which will disable console colors, enable "dumb" mode, tell RouterOS not to try detecting terminal capabilities and set terminal width to 1024 columns. See article `Console login process `_ in MikroTik wiki for more information. Example CLI task diff --git a/docs/docsite/rst/network/user_guide/platform_slxos.rst b/docs/docsite/rst/network/user_guide/platform_slxos.rst index f433599ca3d..4c4145130ca 100644 --- a/docs/docsite/rst/network/user_guide/platform_slxos.rst +++ b/docs/docsite/rst/network/user_guide/platform_slxos.rst @@ -25,7 +25,7 @@ Connections available accepts ``-u myuser -k`` if using password - Indirect Access via a bastion (jump host) + Indirect Access by a bastion (jump host) Connection Settings ``ansible_connection: ansible.netcommon.network_cli`` @@ -56,7 +56,7 @@ Example CLI ``group_vars/slxos.yml`` - If you are using SSH keys (including an ssh-agent) you can remove the ``ansible_password`` configuration. - If you are accessing your host directly (not through a bastion/jump host) you can remove the ``ansible_ssh_common_args`` configuration. -- If you are accessing your host through a bastion/jump host, you cannot include your SSH password in the ``ProxyCommand`` directive. To prevent secrets from leaking out (for example in ``ps`` output), SSH does not support providing passwords via environment variables. +- If you are accessing your host through a bastion/jump host, you cannot include your SSH password in the ``ProxyCommand`` directive. To prevent secrets from leaking out (for example in ``ps`` output), SSH does not support providing passwords through environment variables. Example CLI task ---------------- diff --git a/docs/docsite/rst/network/user_guide/platform_voss.rst b/docs/docsite/rst/network/user_guide/platform_voss.rst index b532e224d5b..172a0530c87 100644 --- a/docs/docsite/rst/network/user_guide/platform_voss.rst +++ b/docs/docsite/rst/network/user_guide/platform_voss.rst @@ -25,7 +25,7 @@ Connections available accepts ``-u myuser -k`` if using password - Indirect Access via a bastion (jump host) + Indirect Access by a bastion (jump host) Connection Settings ``ansible_connection: ansible.netcommon.network_cli`` @@ -59,7 +59,7 @@ Example CLI ``group_vars/voss.yml`` - If you are using SSH keys (including an ssh-agent) you can remove the ``ansible_password`` configuration. - If you are accessing your host directly (not through a bastion/jump host) you can remove the ``ansible_ssh_common_args`` configuration. -- If you are accessing your host through a bastion/jump host, you cannot include your SSH password in the ``ProxyCommand`` directive. To prevent secrets from leaking out (for example in ``ps`` output), SSH does not support providing passwords via environment variables. +- If you are accessing your host through a bastion/jump host, you cannot include your SSH password in the ``ProxyCommand`` directive. To prevent secrets from leaking out (for example in ``ps`` output), SSH does not support providing passwords through environment variables. Example CLI task ---------------- diff --git a/docs/docsite/rst/network/user_guide/platform_vyos.rst b/docs/docsite/rst/network/user_guide/platform_vyos.rst index 5ec00f7bea0..f101fe778c5 100644 --- a/docs/docsite/rst/network/user_guide/platform_vyos.rst +++ b/docs/docsite/rst/network/user_guide/platform_vyos.rst @@ -24,7 +24,7 @@ Connections available accepts ``-u myuser -k`` if using password - Indirect Access via a bastion (jump host) + Indirect Access by a bastion (jump host) Connection Settings ``ansible_connection: ansible.netcommon.network_cli`` @@ -55,7 +55,7 @@ Example CLI ``group_vars/vyos.yml`` - If you are using SSH keys (including an ssh-agent) you can remove the ``ansible_password`` configuration. - If you are accessing your host directly (not through a bastion/jump host) you can remove the ``ansible_ssh_common_args`` configuration. -- If you are accessing your host through a bastion/jump host, you cannot include your SSH password in the ``ProxyCommand`` directive. To prevent secrets from leaking out (for example in ``ps`` output), SSH does not support providing passwords via environment variables. +- If you are accessing your host through a bastion/jump host, you cannot include your SSH password in the ``ProxyCommand`` directive. To prevent secrets from leaking out (for example in ``ps`` output), SSH does not support providing passwords through environment variables. Example CLI task ---------------- diff --git a/docs/docsite/rst/network/user_guide/platform_weos4.rst b/docs/docsite/rst/network/user_guide/platform_weos4.rst index 1a3c79e2a85..dd5dc83290d 100644 --- a/docs/docsite/rst/network/user_guide/platform_weos4.rst +++ b/docs/docsite/rst/network/user_guide/platform_weos4.rst @@ -25,7 +25,7 @@ Connections available accepts ``-u myuser -k`` if using password - Indirect Access via a bastion (jump host) + Indirect Access by a bastion (jump host) Connection Settings ``ansible_connection: community.netcommon.network_cli`` @@ -55,7 +55,7 @@ Example CLI ``group_vars/weos4.yml`` - If you are using SSH keys (including an ssh-agent) you can remove the ``ansible_password`` configuration. - If you are accessing your host directly (not through a bastion/jump host) you can remove the ``ansible_ssh_common_args`` configuration. -- If you are accessing your host through a bastion/jump host, you cannot include your SSH password in the ``ProxyCommand`` directive. To prevent secrets from leaking out (for example in ``ps`` output), SSH does not support providing passwords via environment variables. +- If you are accessing your host through a bastion/jump host, you cannot include your SSH password in the ``ProxyCommand`` directive. To prevent secrets from leaking out (for example in ``ps`` output), SSH does not support providing passwords through environment variables. Example CLI task ----------------