mirror of
https://github.com/ansible-collections/community.general.git
synced 2025-07-23 05:10:22 -07:00
Add a code-smell test for smart quotes and remove smart quotes from all files
This commit is contained in:
parent
f9370c95d7
commit
c82cf791dd
41 changed files with 147 additions and 120 deletions
|
@ -39,7 +39,7 @@ description:
|
|||
The CNOS command is passed as an argument of the method.
|
||||
This module functions the same as the cnos_command module.
|
||||
The only exception is that the following inventory variable can be specified
|
||||
[“condition = <flag string>”]
|
||||
["condition = <flag string>"]
|
||||
When this inventory variable is specified as the variable of a task, the command is executed for
|
||||
the network element that matches the flag string. Usually, commands are executed across a group
|
||||
of network devices. When there is a requirement to skip the execution of the command on one or
|
||||
|
|
|
@ -39,7 +39,7 @@ description:
|
|||
The configuration source can be a set of commands or a template written in the Jinja2 templating language.
|
||||
This module functions the same as the cnos_template module.
|
||||
The only exception is that the following inventory variable can be specified
|
||||
[“condition = <flag string>”]
|
||||
["condition = <flag string>"]
|
||||
When this inventory variable is specified as the variable of a task, the template is executed for
|
||||
the network element that matches the flag string. Usually, templates are used when commands are the
|
||||
same across a group of network devices. When there is a requirement to skip the execution of the
|
||||
|
|
|
@ -33,7 +33,7 @@ module: cnos_factory
|
|||
author: "Dave Kasberg (@dkasberg)"
|
||||
short_description: Reset the switch's startup configuration to default (factory) on devices running Lenovo CNOS
|
||||
description:
|
||||
- This module allows you to reset a switch’s startup configuration. The method provides a way to reset the
|
||||
- This module allows you to reset a switch's startup configuration. The method provides a way to reset the
|
||||
startup configuration to its factory settings. This is helpful when you want to move the switch to another
|
||||
topology as a new network device.
|
||||
This module uses SSH to manage network device configuration.
|
||||
|
|
|
@ -35,7 +35,7 @@ short_description: Perform firmware upgrade/download from a remote server on dev
|
|||
description:
|
||||
- This module allows you to work with switch firmware images. It provides a way to download a firmware image
|
||||
to a network device from a remote server using FTP, SFTP, TFTP, or SCP. The first step is to create a directory
|
||||
from where the remote server can be reached. The next step is to provide the full file path of the image’s
|
||||
from where the remote server can be reached. The next step is to provide the full file path of the image's
|
||||
location. Authentication details required by the remote server must be provided as well. By default, this
|
||||
method makes the newly downloaded firmware image the active image, which will be used by the switch during the
|
||||
next restart.
|
||||
|
|
|
@ -38,9 +38,9 @@ description:
|
|||
of a switch from a remote server. This is achieved by using startup or running configurations of the target
|
||||
device that were previously backed up to a remote server using FTP, SFTP, TFTP, or SCP.
|
||||
The first step is to create a directory from where the remote server can be reached. The next step is to
|
||||
provide the full file path of the backup configuration’s location. Authentication details required by the
|
||||
provide the full file path of the backup configuration's location. Authentication details required by the
|
||||
remote server must be provided as well.
|
||||
By default, this method overwrites the switch’s configuration file with the newly downloaded file.
|
||||
By default, this method overwrites the switch's configuration file with the newly downloaded file.
|
||||
This module uses SSH to manage network device configuration.
|
||||
The results of the operation will be placed in a directory named 'results'
|
||||
that must be created by the user in their local directory to where the playbook is run.
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue