wti.remote.cpm_firmware_info lookup – Get firmware information from WTI OOB and PDU devices
Note
This lookup plugin is part of the wti.remote collection (version 1.0.4).
You might already have this collection installed if you are using the ansible
package.
It is not included in ansible-core
.
To check whether it is installed, run ansible-galaxy collection list
.
To install it, use: ansible-galaxy collection install wti.remote
.
To use it in a playbook, specify: wti.remote.cpm_firmware_info
.
New in version 2.9.0: of wti.remote
Parameters
Parameter |
Comments |
---|---|
This is the Password of the WTI device to send the module. |
|
This is the URL of the WTI device to send the module. |
|
This is the Username of the WTI device to send the module. |
|
Designates to use an https connection or http connection. Choices:
|
|
Flag to control if the lookup will observe HTTP proxy environment variables when present. Choices:
|
|
If false, SSL certificates will not be validated. This should only be used on personally controlled sites using self-signed certificates. Choices:
|
Examples
- name: Get the Firmware Information for a WTI device
cpm_firmware_info:
cpm_url: "nonexist.wti.com"
cpm_username: "super"
cpm_password: "super"
use_https: true
validate_certs: false
- name: Get the Firmware Information for a WTI device
cpm_firmware_info:
cpm_url: "nonexist.wti.com"
cpm_username: "super"
cpm_password: "super"
use_https: false
validate_certs: false
Return Values
Common return values are documented here, the following are the fields unique to this lookup:
Key |
Description |
---|---|
The output JSON returned from the commands sent Returned: always |
|
Current family type (Console = 1 or Power = 0) of the WTI device. Returned: success Sample: “1” |
|
If WTI device is a no FIPS only device. Returned: success Sample: “2020-02-24T20:54:03+00:00” |
|
Current Firmware version of the WTI device. Returned: success Sample: “6.60” |
|
Return status after module completion Returned: always Sample: {“code”: “0”, “text”: “OK”} |
Authors
Western Telematic Inc. (@wtinetworkgear)
Hint
Configuration entries for each entry type have a low to high priority order. For example, a variable that is lower in the list will override a variable that is higher up.