[PR #2586/3464ee29 backport][stable-2.18] Update networking jumphost examples #2594
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a backport of PR #2586 as merged into devel (3464ee2).
The
ansible.netcommon.network_cli
connection plugin uses theansible.netcommon.libssh
connection plugin or falls back toansible.builtin.paramiko
.In ansible-core 2.18, the
ansible.builtin.paramiko
connection no longer uses the variableansible_ssh_common_args
to configure a jumphost, and instead requires the variableansible_paramiko_proxy_command
(which is compatible withansible.netcommon.libssh
in ansible.netcommon >= 2.2.0 too).Using the wrong variable could cause issues like https://forum.ansible.com/t/while-running-playbook-ansible-is-not-using-the-proxy/42323.
I also fixed the example for
ansible.netcommon.netconf
, which never appears to have never supportedansible_ssh_common_args
, but does supportansible_paramiko_proxy_command
andansible_netconf_proxy_command
to configure a jumphost.