It means that single command will execute two functions. The second function will be executed if the retcode of the first one is "success". So it will emulate immediate CISCO-commands.
Also you can patch the klish's sysrepo plugin to make special
function that "set" and immediate "commit" the changes. It's not
difficult because code already contains functions for the "set"
and "commit".
But probably it will be slowly. The "commit" is not klish feature
but sysrepo's feature. It firstly validates configuration and then
commits. It's not fast. So another engine (not klish) with sysrepo
and YANG will be slow too.
It's your own decision but I recommend Juniper-like scheme for
YANG configuration - with commit. The Juniper-like scheme allows
to make configuration more consistent.
2) Yes it's possible to start klish with "configuration" mode
VIEW without "command"/"enable" mode VIEW and "do", "show"
commands. But I don't understand your question about "set"
command. Configuration mode needs "set" command because there is
"del" command to remove configuration fields. How to differentiate
these functions without "set"/"del" commands?
15.10.2024 08:18, Vivek Singh пишет:
--
You received this message because you are subscribed to the Google Groups "klish" group.
To unsubscribe from this group and stop receiving emails from it, send an email to klish+un...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/klish/98dbfbde-27bd-4870-9d6d-3d8eccfe7978n%40googlegroups.com.