@Johnny Karms Pedersen, understood regarding the need for the transaction to be committed before the callback. A simple nano service plan:
ncs:plan-outline my-plan {
ncs:component-type "my-ns-prefix:my-plan-component-type-id" {
ncs:stat...
Do you need a nano service for that? Or perhaps using the post-modification callback is enough?https://developer.cisco.com/docs/nso/guides/services-deep-dive/#service-callbacksExample:examples.ncs/development-guide/services/iface-postmod-py
One variant to avoid this issue is to have a separate service read and set (take ownership) of the "day 0 configuration" so that another service will not delete it.
The same issue applies whether you use YANG augmentation or separate packages. The NSO service manager assumes only one service point in a YANG schema tree. When a YANG list or presence container is tagged with a service point extension, NSO will dis...
