This module provides declarative management of the local usernames configured on Lenovo CNOS devices. It allows playbooks to manage either individual usernames or the collection of usernames in the current running config. It also supports purging usernames from the configuration that are not explicitly defined.
The set of username objects to be configured on the remote Lenovo CNOS device. The list entries can either be the username or a hash of username and properties. This argument is mutually exclusive with the name argument.
aliases: users, collection
configured_password
-
The password to be configured on the network device. The password needs to be provided in cleartext and it will be encrypted on the device. Please note that this option is not same as provider password.
name
-
The username to be configured on the remote Lenovo CNOS device. This argument accepts a string value and is mutually exclusive with the aggregate argument.
purge
boolean
Choices:
no ←
yes
The purge argument instructs the module to consider the resource definition absolute. It will remove any previously configured usernames on the device with the exception of the `admin` user which cannot be deleted per cnos constraints.
role
-
The role argument configures the role for the username in the device running configuration. The argument accepts a string value defining the role name. This argument does not check if the role has been configured on the device.
aliases: roles
sshkey
-
The sshkey argument defines the SSH public key to configure for the username. This argument accepts a valid SSH key value.
state
-
Choices:
present ←
absent
The state argument configures the state of the username definition as it relates to the device operational configuration. When set to present, the username(s) should be configured in the device active configuration and when set to absent the username(s) should not be in the device active configuration
update_password
-
Choices:
on_create
always ←
Since passwords are encrypted in the device running config, this argument will instruct the module when to change the password. When set to always, the password will always be updated in the device and when set to on_create the password will be updated only if the username is created.
-name:create a new usercnos_user:name:ansiblesshkey:"{{lookup('file','~/.ssh/id_rsa.pub')}}"state:present-name:remove all users except admincnos_user:purge:yes-name:set multiple users roleaggregate:-name:netop-name:netendrole:network-operatorstate:present