Skip to content

Improve CLI UX for no enabled command #1119

@troglobit

Description

@troglobit

Description

The no enable command removes the configuration, but for a YANG model that has a default True for the enabled node will result in enabling the feature.

A suggestion, as discussed in #1105, is to extend klish-plugin-sysrepo with additional output for the no command. Example:

admin@example:/config/> no container foo
Removed config node /container[name="foo"]
admin@example:/config/> 

and

admin@example:/config/> no container foo enabled
Removed config node /container[name="foo"]/enabled
NOTE: /container[name="foo"]/enabled default is True!
admin@example:/config/> 

Additional Information

Related to #1105

General Information

Anyone can help out by sponsoring development of new features or contributing pull requests.
Please use this issue for discussions related to the feature.

Metadata

Metadata

Assignees

Labels

enhancementNew feature or request

Type

No type

Projects

Status

Done

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions