corrects Junos network_cli example & variables (#38601) (#38705)

* corrects Junos network_cli example & variables

* vdacosta feedback, thanks

docs/docsite/rst/network/user_guide/platform_junos.rst

@@ -32,21 +32,22 @@ Connections Available
 | |                          | |                                                      | | xml: ``result[1].rpc-reply.interface-information[0].physical-interface[0].name[0].data foo lo0`` |
 +----------------------------+--------------------------------------------------------+----------------------------------------------------------------------------------------------------+
 
-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.
+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.5
 ================================================================================
 
-Example CLI ``group_vars/junos.yml``
-------------------------------------
+Example CLI inventory ``[junos:vars]``
+--------------------------------------
 
 .. code-block:: yaml
 
-   ansible_connection: network_cli
-   ansible_network_os: junos
-   ansible_user: myuser
-   ansible_ssh_pass: !vault...
-   ansible_ssh_common_args: '-o ProxyCommand="ssh -W %h:%p -q bastion01"'
+   [junos:vars]
+   ansible_connection=network_cli
+   ansible_network_os=junos
+   ansible_user=myuser
+   ansible_ssh_pass=!vault...
+   ansible_ssh_common_args='-o ProxyCommand="ssh -W %h:%p -q bastion01"'
 
 
 - If you are using SSH keys (including an ssh-agent) you can remove the ``ansible_ssh_pass`` configuration.
@@ -58,10 +59,9 @@ Example CLI Task
 
 .. code-block:: yaml
 
-   - name: Backup current switch config (junos)
-     junos_config:
-       backup: yes
-     register: backup_junos_location
+   - name: Retrieve Junos OS version
+     junos_command:
+       commands: show version
      when: ansible_network_os == 'junos'
 
 
@@ -76,26 +76,28 @@ 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 ``junos_netconf`` module via the CLI connection. Set up group_vars/junos.yml just like in the CLI example above, then run a playbook task like this:
+To enable NETCONF on a new switch via Ansible, use the ``junos_netconf`` module via 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
 
    - name: Enable NETCONF
+     connection: network_cli
      junos_netconf:
      when: ansible_network_os == 'junos'
 
-Once NETCONF is enabled, change your ``group_vars/junos.yml`` to use the NETCONF connection.
+Once NETCONF is enabled, change your variables to use the NETCONF connection.
 
-Example NETCONF ``group_vars/junos.yml``
-----------------------------------------
+Example NETCONF inventory ``[junos:vars]``
+------------------------------------------
 
 .. code-block:: yaml
 
-   ansible_connection: netconf
-   ansible_network_os: junos
-   ansible_user: myuser
-   ansible_ssh_pass: !vault | 
-   ansible_ssh_common_args: '-o ProxyCommand="ssh -W %h:%p -q bastion01"'
+   [junos:vars]
+   ansible_connection=netconf
+   ansible_network_os=junos
+   ansible_user=myuser
+   ansible_ssh_pass=!vault | 
+   ansible_ssh_common_args='-o ProxyCommand="ssh -W %h:%p -q bastion01"'
 
 
 Example NETCONF Task