I have a Service Package with two separate Servicepoints, under certain conditions, I need to trigger the second servicepoint from the request coming in the first service point, e.g.:
Container Parent {
List A {
ncs:servicepoint
....
}
List B {
ncs:servicepoint
....
}
}
Inside the Python Service package, If we send request on servicepoint B, some condition may require servicepoint A to be re-applied, we have tried the use of touch(), re-deploy, as well as modifying the tree under servicepoint A, but that action does not get triggered.
What's curious is when if I perform a re-deploy on servicepoint B after committing my changes (from CLI, or explicitly setting the "deep" option in restconf api), the changes do get applied. Re-deploy shallow does not trigger the second servicepoint.
I would prefer to have all my changes in a single transaction, but I am not sure what's the limitation that is preventing this behavior and if the alternative is using kickers or separate external requests, then we may have to live with that.
Appreciate anyone that has any insight!
