Documentation

eos_template - Manage Arista EOS device configurations

New in version 2.1.

Synopsis

Manages network device configurations over SSH or eAPI. This module allows implementors to work with the device running-config. It provides a way to push a set of commands onto a network device by evaluting the current running-config and only pushing configuration commands that are not already configured. The config source can be a set of commands or a template.

Options

parameter required default choices comments
auth_pass
no none
    Specifies the password to use if required to enter privileged mode on the remote device. If authorize is false, then this argument does nothing. If the value is not specified in the task, the value of environment variable ANSIBLE_NET_AUTH_PASS will be used instead.
    authorize
    no
    • yes
    • no
    Instructs the module to enter priviledged mode on the remote device before sending any commands. If not specified, the device will attempt to excecute all commands in non-priviledged mode. If the value is not specified in the task, the value of environment variable ANSIBLE_NET_AUTHORIZE will be used instead.
    backup
    no
    • yes
    • no
    When this argument is configured true, the module will backup the running-config from the node prior to making any changes. The backup file will be written to backup_{{ hostname }} in the root of the playbook directory.
    config
    no
      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 config argument allows the implementer to pass in the configuruation to use as the base config for comparision.
      force
      no
      • yes
      • no
      The force argument instructs the module to not consider the current devices running-config. When set to true, this will cause the module to push the contents of src into the device without first checking if already configured.
      host
      yes
        Specifies the DNS host name or address for connecting to the remote device over the specified transport. The value of host is used as the destination address for the transport.
        include_defaults
        no
        • yes
        • no
        By default when the eos_template connects to the remote device to retrieve the configuration it will issue the `show running-config` command. If this option is set to True then the issued command will be `show running-config all`
        password
        no
          Specifies the password to use to authenticate the connection to the remote device. This is a common argument used for either cli or eapi transports. If the value is not specified in the task, the value of environment variable ANSIBLE_NET_PASSWORD will be used instead.
          port
          no 0 (use common port)
            Specifies the port to use when buiding the connection to the remote device. This value applies to either cli or eapi. The port value will default to the approriate transport common port if none is provided in the task. (cli=22, http=80, https=443).
            provider
            no
              Convience method that allows all eos arguments to be passed as a dict object. All constraints (required, choices, etc) must be met either by individual arguments or values in this dict.
              replace
              no
              • yes
              • no
              This argument will cause the provided configuration to be replaced on the destination node. The use of the replace argument will always cause the task to set changed to true and will implies force is true. This argument is only valid with transport is eapi.
              src
              yes
                The path to the config source. The source can be either a file with config or a template that will be merged during runtime. By default the task will search for the source file in role or playbook root folder in templates directory.
                ssh_keyfile
                no
                  Specifies the SSH keyfile to use to authenticate the connection to the remote device. This argument is only used for cli transports. If the value is not specified in the task, the value of environment variable ANSIBLE_NET_SSH_KEYFILE will be used instead.
                  transport
                  yes cli
                    Configures the transport connection to use when connecting to the remote device. The transport argument supports connectivity to the device over cli (ssh) or eapi.
                    use_ssl
                    no True
                    • yes
                    • no
                    Configures the transport to use SSL if set to true only when the transport argument is configured as eapi. If the transport argument is not eapi, this value is ignored
                    username
                    no
                      Configures the usename to use to authenticate the connection to the remote device. The value of username is used to authenticate either the CLI login or the eAPI authentication depending on which transport is used. If the value is not specified in the task, the value of environment variable ANSIBLE_NET_USERNAME will be used instead.

                      Examples

                      - name: push a configuration onto the device
                        eos_template:
                          src: config.j2
                      
                      - name: forceable push a configuration onto the device
                        eos_template:
                          src: config.j2
                          force: yes
                      
                      - name: provide the base configuration for comparision
                        eos_template:
                          src: candidate_config.txt
                          config: current_config.txt
                      

                      Return Values

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

                      name description returned type sample
                      updates The set of commands that will be pushed to the remote device always list ['...', '...']
                      responses The set of responses from issuing the commands on the device list ['...', '...']


                      This is a Core Module

                      For more information on what this means please read Core Modules

                      For help in developing on modules, should you be so inclined, please read Community Information & Contributing, Helping Testing PRs and Developing Modules.