Hi all,
grepyang has got a new feature: it could grep for a node through a module:
# ./grepyang cancel-commit ietf-netc...@2011-06-01.yang
853: rpc cancel-commit {
854: if-feature confirmed-commit;
855: description
856: "This operation is used to cancel an ongoing confirmed commit.
857: If the confirmed commit is persistent, the parameter
858: 'persist-id' must be given, and it must match the value of the
859: 'persist' parameter.";
860: reference "RFC 6241, Section 8.4.4.1";
861:
862: input {
863: leaf persist-id {
864: type string;
865: description
866: "This parameter is given in order to cancel a persistent
867: confirmed commit. The value must be equal to the value
868: given in the 'persist' parameter to the <commit> operation.
869: If it does not match, the operation fails with an
870: 'invalid-value' error.";
871: }
872: }
873: }
Now it can grep for a node with a greped node:
# ./grepyang input cancel-commit ietf-netc...@2011-06-01.yang
853: rpc cancel-commit {
862: input {
863: leaf persist-id {
864: type string;
865: description
866: "This parameter is given in order to cancel a persistent
867: confirmed commit. The value must be equal to the value
868: given in the 'persist' parameter to the <commit> operation.
869: If it does not match, the operation fails with an
870: 'invalid-value' error.";
871: }
872: }
873: }
pyang lacks such features; that's why I have been working on grepyang.
It is out on Github (https://github.com/ariel-anieli/grepyang); feel
free to play around with it.
If you find it of any interest, have some remarks, or see it needs
enhancements; please, do so: I will work on the issues.
Regards,
Ariel
-------------------------------------------------------------------------------
This message was sent using EURECOM Webmail: http://webmail.eurecom.fr
_______________________________________________
netmod mailing list
netmod@ietf.org
https://www.ietf.org/mailman/listinfo/netmod
