Is there a way to replace a CDB during runtime to accommodate a backwards-incompatible change in the yang model while performing a software upgrade?
Referring to the NSO Dev CDB guide:
"In NSO the schema is the data model stored in the .fxs files. Once CDB has initialized it also stores a copy of the schema associated with the data it holds.
Every time NSO starts, CDB will check the current contents of the .fxs files with its own copy of the schema files. If CDB detects any changes in the schema it initiates an upgrade transaction. In the simplest case, CDB automatically resolves the changes and commits the new data before NSO reaches start-phase one."
The above snippet from NSO CDB docs is applying to backwards-compatible changes only, in other cases, the upgrade would fail.
Can we write a script to check the old yang contents vs new ones and replace the cdb before loading them onto the NSO during a software upgrade?
