Show status Statement in CLI

[dimitra]

Hi,

Does CLI support the status Statement as described here: https://tools.ietf.org/html/rfc6020#section-7.19.2?

If I have a yang file where a parameter is obsolete or deprecated will I be able to get this info from CLI?

BR,
Dimitra

[cohult]

Hi,

The status statement is considered information to the reader of the YANG model. Nodes are put as “status current” by default as RFC 6020 / 7950 specifies, and ConfD make no difference between “current”, “deprecated” and “obsolete” nodes. The information is not shown in the CLI.

One way to show this information in the CLI would ge to make use of the tailf:info statement. See ConfD UG 6.5 3.8.1. Custom Help Texts.

If you want to prevent obsoleted and/or deprecated nodes from being shown or exported to a file when the configuration is saved could be to use a hide group, one for deprecated and one for obsolete and hide one or both of them before saving the config.
Example:

  leaf autumn {
    type string;
    description "DEPRECATED: a pretty autumn leaf";
    tailf:info "DEPRECATED: a pretty autumn leaf";
    status deprecated;
    tailf:hidden deprecated;
  }

Note that if a hide group is visible then those nodes are accepted, but if it is not visible then the nodes are not accepted with for example the load command.

It is possible to create a validation callback which uses the CONFD_VALIDATION_WARN or CONFD_ERR results and then give back a warning or error to the user if a deprecated/obsoleted node is being configured, perhaps in combination with the tailf:meta-data and tailf:meta-value statements.

[melissop]

Hello,

Does ConfD expose the status statement information, described in RFC 6020, via any of the APIs?
e.g. using confd_load_schemas() and confd_cs_node_info struct.

BR,
Tasos

[cohult]

Hi,
The status statement is not included in the schema information.
But as I mentioned in the reply you can add it using tailf:meta-data and tailf:meta-value statements.

See these topics for inspiration:

Is the schema range available via confd_cs_node_info?

Hi Peter! The range statement is not included in the schema information. If you want that information in the schema information you can for example use the tailf:meta-data extension to provide key+value information for the node in the schema. I put together a small tailf:meta-data + tailf:meta-value + cdb_get_modifications() example that add an annotated yang model with the tailf:meta-data key+value statements, see my-yang-ann.yang, and a subscriber, see sub.c. When a subscription event occur,…

Maapi_request_action and tailf:confirm text

Consider a custom northbound interface invoking maapi_request_action APIs (no CLI in this use case), and a backend that processes the action requests via action callback. How does the northbound interface (written using maapi APIs) issue the confirmation?

How to know the named type of NavuLeaf

The typedef information is not included in the schema information. But you can use the tailf:meta-data extension to for example do something like this (using the 1-2-3-start-query-model example): container dhcp { ... typedef loglevel { type enumeration { enum kern; enum mail; enum local7; } } ... leaf logFacility { tailf:meta-data "typedef loglevel" { tailf:meta-value "type enumeration"; } type loglevel; default local…