amnesh.soodar.soodar_config module – Manage Amnesh Soodar configuration sections

Note

This module is part of the amnesh.soodar collection (version 1.0.0).

To install it, use: ansible-galaxy collection install https://soodar.ir/ansible/amnesh.soodar.tar.gz.

To use it in a playbook, specify: amnesh.soodar.soodar_config.

New in amnesh.soodar 1.0.0

Synopsis 

Amnesh Soodar configurations use a simple block indent file syntax for segmenting configuration into sections. This module provides an implementation for working with Soodar configuration sections in a deterministic way.

Note

This module has a corresponding action plugin.

Parameters 

Parameter	Comments
after list / elements=string	The ordered set of commands to append to the end of the command stack if a change needs to be made. Just like with before this allows the playbook designer to append a set of commands to be executed after the command set.
backup boolean	This argument will cause the module to create a full backup of the current `running-config` from the remote device before any changes are made. If the `backup_options` value is not given, the backup file is written to the `backup` folder in the playbook root directory or role root directory, if playbook is part of an ansible role. If the directory does not exist, it is created. Choices: `false` ← (default) `true`
backup_options dictionary	This is a dict object containing configurable options related to backup file path. The value of this option is read only when `backup` is set to yes, if `backup` is set to no this option will be silently ignored.
dir_path path	This option provides the path ending with directory name in which the backup configuration file will be stored. If the directory does not exist it will be first created and the filename is either the value of `filename` or default filename as described in `filename` options description. If the path value is not given in that case a backup directory will be created in the current working directory and backup configuration will be copied in `filename` within backup directory.
filename string	The filename to be used to store the backup configuration. If the filename is not given it will be generated based on the hostname, current time and date in format defined by <hostname>_config.<current-date>@<current-time>
before list / elements=string	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.
diff_against string	When using the `ansible-playbook --diff` command line argument the module can generate diffs against different sources. When this option is configure as startup, the module will return the diff of the running-config against the startup-config. When this option is configured as intended, the module will return the diff of the running-config against the configuration provided in the `intended_config` argument. When this option is configured as running, the module will return the before and after diff of the running-config with respect to any changes made to the device configuration. Choices: `"running"` `"startup"` `"intended"`
diff_ignore_lines list / elements=string	Use this argument to specify one or more lines that should be ignored during the diff. This is used for lines in the configuration that are automatically updated by the system. This argument takes a list of regular expressions or exact line matches.
intended_config string	The `intended_config` provides the master configuration that the node should conform to and is used to check the final running-config against. This argument will not modify any settings on the remote device and is strictly used to check the compliance of the current device’s configuration against. When specifying this argument, the task should also modify the `diff_against` value and set it to intended. The configuration lines for this value should be similar to how it will appear if present in the running-configuration of the device including the indentation to ensure correct diff.
lines aliases: commands list / elements=string	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 to ensure idempotency and correct diff. Be sure to note the configuration command syntax as some commands are automatically modified by the device config parser.
match string	Instructs the module on the way to perform the matching of the set of commands against the current device config. If match is set to line, commands are matched line by line. If match is set to strict, command lines are matched with respect to position. If match is set to exact, command lines must be an equal match. Finally, if match is set to none, the module will not attempt to compare the source configuration with the running configuration on the remote device. Choices: `"line"` ← (default) `"strict"` `"exact"` `"none"`
parents list / elements=string	The ordered set of parents that uniquely identify the section or hierarchy the commands should be checked against. If the parents argument is omitted, the commands are checked against the set of top level or global commands.
replace string	Instructs the module on the way to perform the configuration on the device. If the replace argument is set to line then the modified lines are pushed to the device in configuration mode. If the replace argument is set to block then the entire command block is pushed to the device in configuration mode if any line is not correct. Choices: `"line"` ← (default) `"block"`
running_config aliases: config string	The module, by default, will connect to the remote device and retrieve the current running-config to use as a base for comparing against the contents of source. There are times when it is not desirable to have the task get the current running-config for every task in a playbook. The running_config argument allows the implementer to pass in the configuration to use as the base config for comparison. The configuration lines for this option should be similar to how it will appear if present in the running-configuration of the device including the indentation to ensure idempotency and correct diff.
save_when string	When changes are made to the device running-configuration, the changes are not copied to non-volatile storage by default. Using this argument will change that before. If the argument is set to always, then the running-config will always be copied to the startup-config and the modified flag will always be set to True. If the argument is set to modified, then the running-config will only be copied to the startup-config if it has changed since the last save to startup-config. If the argument is set to never, the running-config will never be copied to the startup-config. If the argument is set to changed, then the running-config will only be copied to the startup-config if the task has made a change. changed was added in Ansible 2.5. Choices: `"always"` `"never"` ← (default) `"modified"` `"changed"`
src string	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 directory. This argument is mutually exclusive with lines, parents. The configuration lines in the source file should be similar to how it will appear if present in the running-configuration of the device including the indentation to ensure idempotency and correct diff.

Notes 

Note

Tested against Soodar 21.04
Abbreviated commands are NOT idempotent.
To ensure idempotency and correct diff the configuration lines in the relevant module options should be similar to how they appear if present in the running configuration on device including the indentation.

Examples 

- name: configure top level configuration
  amnesh.soodar.soodar_config:
    lines: hostname {{ inventory_hostname }}

- name: configure interface settings
  amnesh.soodar.soodar_config:
    lines:
    - description test interface
    - ip address 172.31.1.1/24
    parents: interface ge1

- name: configure ip MTU on multiple interfaces
  amnesh.soodar.soodar_config:
    lines:
    - ip mtu 2000
    parents: '{{ item }}'
  with_items:
  - interface ge1
  - interface ge2
  - interface tunnel20

- name: configure policer in Scavenger class
  amnesh.soodar.soodar_config:
    lines:
    - police cir 64000 conform-action transmit exceed-action drop
    parents:
    - policy-map Foo
    - class Scavenger

- name: load new acl into device
  amnesh.soodar.soodar_config:
    lines:
    - 10 permit ip 192.0.2.1/24 any
    - 20 permit ip 192.0.2.2/24 any
    - 30 permit ip 192.0.2.3/24 any
    - 40 permit ip 192.0.2.4/24 any
    - 50 permit ip 192.0.2.5/24 any
    parents: ip access-list test
    before: no ip access-list test
    match: exact

- name: check the running-config against master config
  amnesh.soodar.soodar_config:
    diff_against: intended
    intended_config: "{{ lookup('file', 'master.cfg') }}"

- name: check the startup-config against the running-config
  amnesh.soodar.soodar_config:
    diff_against: startup
    diff_ignore_lines:
    - ntp server .*

- name: save running to startup when modified
  amnesh.soodar.soodar_config:
    save_when: modified

- name: for idempotency, use full-form commands
  amnesh.soodar.soodar_config:
    lines:
      # - shut
    - shutdown
    parents: interface ge1

- name: render a Jinja2 template onto a Soodar device
  amnesh.soodar.soodar_config:
    backup: yes
    src: ios_template.j2

- name: configurable backup path
  amnesh.soodar.soodar_config:
    src: ios_template.j2
    backup: yes
    backup_options:
      filename: backup.cfg
      dir_path: /home/user

Return Values 

Common return values are documented here, the following are the fields unique to this module:

Key	Description
backup_path string	The full path to the backup file Returned: when backup is yes Sample: `"/playbooks/ansible/backup/ios_config.2016-07-16@22:28:34"`
commands list / elements=string	The set of commands that will be pushed to the remote device Returned: always Sample: `["hostname foo", "router ospf 1", "router-id 192.0.2.1"]`
date string	The date extracted from the backup file name Returned: when backup is yes Sample: `"2020-07-16"`
filename string	The name of the backup file Returned: when backup is yes and filename is not specified in backup options Sample: `"ios_config.2016-07-16@22:28:34"`
shortname string	The full path to the backup file excluding the timestamp Returned: when backup is yes and filename is not specified in backup options Sample: `"/playbooks/ansible/backup/ios_config"`
time string	The time extracted from the backup file name Returned: when backup is yes Sample: `"22:28:34"`
updates list / elements=string	The set of commands that will be pushed to the remote device Returned: always Sample: `["hostname foo", "router ospf 1", "router-id 192.0.2.1"]`

Authors

Mahdi Varasteh (@m-varasteh)

Collection links

Issue Tracker Homepage

amnesh.soodar.soodar_config module – Manage Amnesh Soodar configuration sections

Synopsis

Parameters

Notes

Examples

Return Values

Authors

Collection links

Synopsis 

Parameters 

Notes 

Examples 

Return Values 