wti.remote.cpm_config_restore lookup – Send operational parameters to 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_config_restore
.
New in version 2.9.0: of wti.remote
Parameters
Parameter |
Comments |
---|---|
This is the filename of the existing WTI device configuration file. |
|
This is the Password of the WTI device to get the parameters from. |
|
This is the directory path to the existing the WTI device configuration file. Default: “/tmp/” |
|
This is the URL of the WTI device to get the parameters from. |
|
This is the Username of the WTI device to get the parameters from. |
|
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 Parameters for a WTI device
cpm_config_restore:
cpm_url: "nonexist.wti.com"
cpm_username: "super"
cpm_password: "super"
cpm_path: "/tmp/"
cpm_filename: "wti-192-10-10-239-2020-02-13T16-05-57-xml"
use_https: true
validate_certs: false
Return Values
Common return values are documented here, the following are the fields unique to this lookup:
Key |
Description |
---|---|
The output XML configuration of the WTI device queried Returned: always |
|
Length of the file uploaded in bytes Returned: success Sample: [{“filelength”: 329439}] |
|
List of status returns from backup operation Returned: success Sample: [{“code”: 0, “text”: “ok”, “unittimestamp”: “2020-02-14T00:18:57+00:00”}] |
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.