Westermo WeOS 4 is part of the community.network collection and only supports CLI connections. This page offers details on how to use ansible.netcommon.network_cli
on WeOS 4 in Ansible.
CLI | |
---|---|
Protocol | SSH |
Credentials |
uses SSH keys / SSH-agent if present accepts |
Indirect Access | via a bastion (jump host) |
Connection Settings |
|
Enable Mode | not supported by WeOS 4 |
Returned Data Format |
|
WeOS 4 does not support ansible_connection: local
. You must use ansible_connection: ansible.netcommon.network_cli
.
group_vars/weos4.yml
ansible_connection: ansible.netcommon.network_cli ansible_network_os: community.network.weos4 ansible_user: myuser ansible_password: !vault... ansible_ssh_common_args: '-o ProxyCommand="ssh -W %h:%p -q bastion01"'
ansible_password
configuration.ansible_ssh_common_args
configuration.ProxyCommand
directive. To prevent secrets from leaking out (for example in ps
output), SSH does not support providing passwords via environment variables.- name: Get version information (WeOS 4) ansible.netcommon.cli_command: commands: "show version" register: show_ver when: ansible_network_os == 'community.network.weos4'
- name: Replace configuration with file on ansible host (WeOS 4) ansible.netcommon.cli_config: config: "{{ lookup('file', 'westermo.conf') }}" replace: "yes" diff_match: exact diff_replace: config when: ansible_network_os == 'community.network.weos4'
Warning
Never store passwords in plain text. We recommend using SSH keys to authenticate SSH connections. Ansible supports ssh-agent to manage your SSH keys. If you must use passwords to authenticate SSH connections, we recommend encrypting them with Ansible Vault.
See also
© 2012–2018 Michael DeHaan
© 2018–2021 Red Hat, Inc.
Licensed under the GNU General Public License version 3.
https://docs.ansible.com/ansible/latest/network/user_guide/platform_weos4.html