New in version 2.2.
parameter | required | default | choices | comments | |||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
after | no | The ordered set of commands to append to the end of the command stack if a change needs to be made. As with before, the playbook desinger can use this to append a set of commands to be executed after the command set. | |||||||||||||||||||||||||||||||||||||
backup | no |
| This argument causes the module to create a full backup of the current running-config from the remote device before any changes are made. The backup file is written to the backup folder in the playbook root directory. If the directory does not exist, it is created. | ||||||||||||||||||||||||||||||||||||
before | no | The ordered set of commands to push on to the command stack if a change needs to be made. This allows the playbook designer the opportunity to perform configuration commands prior to pushing any changes without affecting how the set of commands are matched against the system. | |||||||||||||||||||||||||||||||||||||
config | no | The playbook designer can use the config argument to supply the base configuration to be used to validate necessary configuration changes. If you specify this argument, the module does not download the running-config from the remote node. | |||||||||||||||||||||||||||||||||||||
lines | no | The ordered set of commands that should be configured in the section. The commands must be the exact same commands as found in the device running-config. Note the configuration command syntax as the device config parser automatically modifies some commands. This argument is mutually exclusive with src. aliases: commands | |||||||||||||||||||||||||||||||||||||
match | no | line |
| Instructs the module on the way to perform the matching of the set of commands against the current device config. If you set match to line, commands match line by line. If you set match to strict, command lines matched by respect to position. If you set match to exact, command lines must be an equal match. Finally, if you set match to none, the module does not attempt to compare the source configuration with the running configuration on the remote device. | |||||||||||||||||||||||||||||||||||
parents | no | The ordered set of parents that uniquely identify the section the commands should be checked against. If you do not specify the parents argument, the commands are checked against the set of top level or global commands. | |||||||||||||||||||||||||||||||||||||
provider | no | A dict object containing connection details. |
|||||||||||||||||||||||||||||||||||||
| |||||||||||||||||||||||||||||||||||||||
replace | no | line |
| Instructs the module on the way to perform the configuration on the device. If you set the replace argument to line, then the modified lines are pushed to the device in configuration mode. If you set the replace argument to block then the entire command block is pushed to the device in configuration mode if any line is not correct. | |||||||||||||||||||||||||||||||||||
save | no |
| The save argument instructs the module to save the running- config to the startup-config at the conclusion of the module running. If you specify check mode, this argument is ignored. | ||||||||||||||||||||||||||||||||||||
src | no | Specifies the source path to the file that contains the configuration or configuration template to load. The path to the source file can either be the full path on the Ansible control host or a relative path from the playbook or role root dir. This argument is mutually exclusive with lines. | |||||||||||||||||||||||||||||||||||||
update | no | merge |
| The update argument controls how the configuration statements are processed on the remote device. Valid choices for the update argument are merge and check. When you set this argument to merge, the configuration changes merge with the current device running configuration. When you set this argument to check the configuration updates are determined but not actually configured on the remote device. |
- dellos6_config: lines: ['hostname {{ inventory_hostname }}'] provider: "{{ cli }}" - dellos6_config: lines: - 10 permit ip 1.1.1.1 any log - 20 permit ip 2.2.2.2 any log - 30 permit ip 3.3.3.3 any log - 40 permit ip 4.4.4.4 any log - 50 permit ip 5.5.5.5 any log parents: ['ip access-list test'] before: ['no ip access-list test'] match: exact provider: "{{ cli }}" - dellos6_config: lines: - 10 permit ip 1.1.1.1 any log - 20 permit ip 2.2.2.2 any log - 30 permit ip 3.3.3.3 any log - 40 permit ip 4.4.4.4 any log parents: ['ip access-list test'] before: ['no ip access-list test'] replace: block provider: "{{ cli }}"
Common return values are documented here Return Values, the following are the fields unique to this module:
name | description | returned | type | sample |
---|---|---|---|---|
saved | Returns whether the configuration is saved to the startup configuration or not. | When not check_mode. | bool | True |
updates | The set of commands pushed to the remote device. | Always. | list | ['...', '...'] |
responses | The set of responses from issuing the commands on the device. | When not check_mode. | list | ['...', '...'] |
This module is flagged as preview which means that it is not guaranteed to have a backwards compatible interface.
For help in developing on modules, should you be so inclined, please read Community Information & Contributing, Testing Ansible and Developing Modules.
© 2012–2017 Michael DeHaan
© 2017 Red Hat, Inc.
Licensed under the GNU General Public License version 3.
https://docs.ansible.com/ansible/latest/dellos6_config_module.html