Joachim Wiberg
6521de28e7
Refactor 0f9d429 to first check if the .cfg file has any routing
protocol active before converting the type's value.
This fixes a regression in the release cycle that otherwise would
cause a fresh startup-config, created from a plain factory-config
from v24.08, to be converted to an empty file.
Inspired by this fix, the same mitigation, albeit highyl unlikely,
has been applied to the v1.0 user shell type migration.
Signed-off-by: Joachim Wiberg <troglobit@gmail.com>
Configuration Daemon
confd is the Infix configuration daemon that serves as the glue
between sysrepo and netopeer2 (NETCONF) and the UNIX system under
it all.
Factory & Failure Config
Infix supports both static and dynamically generated factory-config. At
boot the dynamic is always generated to /run/confd/factory-config.gen,
which is installed to /etc/factory-config.cfg and used by default, if
that file does not already exist. The same applies to the failure mode
configuration.
The following describes how a vendor/product specific config is found
and installed into /etc/factory-config.cfg before the dynamic one is
installed.
/etc/factory-config.cfg: built into the image, e.g., r2s/usr/share/product/<PRODUCT>/etc/factory-config.cfg, where the<PRODUCT>is determined from the VPD, which is available afterprobehas run, in/run/system.jsonas"product-name". The lower case version of the string is used
In the second option a script running just after probe will in fact
cp the complete product specific directory to /, meaning any file
and directory that is writable at runtime can be overloaded with device
specific versions.
Origin & References
Based on the Open Source dklibc/sysrepo_plugin_ietf_system project by Denis Kalashnikov.