mirror of
https://github.com/ansible-collections/community.general.git
synced 2025-07-22 12:50:22 -07:00
junos_config documentation missing "update" choice (#51299)
* Update junos_config.py The current junos_config module documentation only lists "merge","override" and "replace" as update parameter choices. Looking into junos_python.py "update" is another option which is really helpful and in my opinion the most needed option. ''' update=dict(default='merge', choices=['merge', 'override', 'replace', 'update']) ''' +label: docsite_pr * Fixup Update junos_config.py The current junos_config module documentation only lists "merge","override" and "replace" as update parameter choices. Looking into junos_python.py "update" is another option which is really helpful and in my opinion the most needed option. ''' update=dict(default='merge', choices=['merge', 'override', 'replace', 'update']) ''' Co-Authored-By: crab86 <sgesenhoff@gmail.com>
This commit is contained in:
parent
8eff4cae10
commit
48107ac212
2 changed files with 7 additions and 2 deletions
|
@ -113,8 +113,14 @@ options:
|
|||
it with the loaded configuration.
|
||||
C(replace) substitutes each hierarchy level in the loaded configuration
|
||||
for the corresponding level.
|
||||
C(update) is similar to the override option. The new configuration completely
|
||||
replaces the existing configuration. The difference comes when the configuration
|
||||
is later committed. This option performs a 'diff' between the new candidate
|
||||
configuration and the existing committed configuration. It then only notifies
|
||||
system processes responsible for the changed portions of the configuration, and
|
||||
only marks the actual configuration changes as 'changed'.
|
||||
default: merge
|
||||
choices: ['merge', 'override', 'replace']
|
||||
choices: ['merge', 'override', 'replace', 'update']
|
||||
version_added: "2.3"
|
||||
confirm_commit:
|
||||
description:
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue