-
Notifications
You must be signed in to change notification settings - Fork 23.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
revises network portion of 2.5 porting guide #37938
Conversation
ansible_become_pass=cisco | ||
ansible_network_os=ios | ||
ansible_password=cisco | ||
ansible_user=cisco | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Worth linking to network docs here again?
------------------------------------------------------------------ | ||
|
||
Ansible 2.5 introduces two persistent connection types, ``network_cli`` and ``netconf``. We recommend you use these whenever possible. | ||
Unless you need a ``local`` connection, update your playbooks to use ``network_cli`` or ``netconf`` and to |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe clarify that local
is needed when using eAPI/NX-API?
Unless you need a ``local`` connection, update your playbooks to use ``network_cli`` or ``netconf`` and to | ||
specify your connection variables with standard Ansible connection variables: | ||
|
||
OLD In Ansible 2.4 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
**OLD** In Ansible 2.4
|
||
We recommend setting connection properties in inventory by group. As you update your playbooks and inventory files, you can easily make the change to ``become`` for privilege escalation (on platforms that support it). For more information, see the :ref:`using become with network modules<become-network>` guide and the :ref:`platform documentation<platform_options>`. To update the ``ios_command`` task above, move the connection properties to inventory like this: | ||
|
||
NEW In Ansible 2.5 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
**NEW** In Ansible 2.5
|
||
Top-level connection arguments like ``username``, ``host``, and ``password`` are deprecated and will be removed in version 2.9. | ||
|
||
OLD In Ansible 2.4 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
**OLD** In Ansible 2.4
|
||
NEW In Ansible 2.5 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
**NEW** In Ansible 2.5
@@ -199,12 +199,16 @@ Porting custom scripts | |||
|
|||
No notable changes. | |||
|
|||
Networking | |||
========== | |||
Network |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think somewhere prominent in this section we should link to the network guide.
Chatted with Scott today - he says "if it looks good to you I'm fine with it." I'm going to take that as a positive review and merge. |
* revises network portion of 2.5 porting guide (cherry picked from commit b72960f)
* revises network portion of 2.5 porting guide (cherry picked from commit b72960f)
* revises network portion of 2.5 porting guide
In |
SUMMARY
Adds more detail, including the persistent connection options to the Network section of the 2.5 Porting Guide.
Fixes #36777
ISSUE TYPE
COMPONENT NAME
ANSIBLE VERSION
2.5 and higher