the yang spec doesn't allow leafref on config node pointing to oper node https://www.rfc-editor.org/rfc/rfc6020.html#section-9.9.2, thus the compiler error.
the config false deviation are dropped because config false nodes in those subtrees don't mak...
I believe sync-from then create the service would bump the refcount on interface{st0} to 2, after which removal of the service doesn't delete interface{st0}, you can check the service-meta-data after service deployment.
that aside, the default operat...
the yang spec https://www.rfc-editor.org/rfc/rfc6020.html#section-7.19.5 doesn't allow access to oper data if the xpath is on a config node, thus the compiler error
can you consider something like contains(/devices/device[name=current()]/device-type/...
take a look at our updated document: https://cisco-tailf.gitbook.io/nso-docs/guides/development/core-concepts/api-overview/python-api-overview#maagic-api
that together with the model of the action(service re-deploy action is defined in tailf-ncs-serv...
1 for config changes pushed to device, there's /ncs-config/logs/audit-network-log, so you don't need to write your own log
2 if you use an action to process logs, you need to consider in rest client <-> nso <-> action callback communication, the payl...