On Sun, Dec 1, 2024 at 10:25 AM Kent Watsen <[email protected]> wrote:
> > > Another option that comes to mind is that the system datastore does > > not feed into anything. Instead, it just exposes the (current) system > > configuration and if someone wants to use it, that someone can copy it > > into running and then takes responsibility for it. > > I do not favor this because it leads to stale definitions. > > For example, the <system> datastore may define a bag of trust anchor > certificates, i.e., <system> implements RFC9641. The bag as a whole is > referenced by <running>, but the bag's contents may change, e.g., when the > device’s software is updated. > > I do not understand how <running> references <system>. How does a config leafref in <running> validate correctly unless the pointed-at leaf is also in <running>? The same issue applies to templates if the incomplete list entry in <running> has any pointed-at leafs. Kent > Andy > > _______________________________________________ > netmod mailing list -- [email protected] > To unsubscribe send an email to [email protected] >
_______________________________________________ netmod mailing list -- [email protected] To unsubscribe send an email to [email protected]
