You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
module: test
+--rw leaf1
+--rw leaf2* [name]
+--rw name string
+--rw value1 string
+--rw value2 string
Is there any possiblity that when a get-config request comes client, can we register a callback so that we can send the custom data instead of the data stored in running database.
Regards,
Sukesh
The text was updated successfully, but these errors were encountered:
That's typically not how sysrepo is used. What problem are you trying to solve this way, and what exactly are your requirements? Are you maybe syncing configs between multiple backends, etc?
Is there any possiblity that when a get-config request comes client, can we register a callback so that we can send the custom data instead of the data stored in running database.
No, this is not possible and should be avoided. Such a design is bypassing the design of NMDA and I am guessing replacing it with something similar. So, you should instead understand the difference between running and operational datastore and then perhaps set some operational datastore callback, if required. Read through the NMDA RFC and understand how it is implemented in sysrepo by reading its docs.
Hi @michalvasko
module: test
+--rw leaf1
+--rw leaf2* [name]
+--rw name string
+--rw value1 string
+--rw value2 string
Is there any possiblity that when a get-config request comes client, can we register a callback so that we can send the custom data instead of the data stored in running database.
Regards,
Sukesh
The text was updated successfully, but these errors were encountered: