When one of the Debian package is reinstalled or upgraded, the configuration files are silently replaced with the package defaults.
Even though the risk is mitigated because petals-esb and petals-registry favour configuration in a specific directory for each instance, the problem still exists for the default-env, default-snmp, the default configurations as well as the CLI's configuration files.
Debian provides a mechanism to handle that and an upgrade will notify the administrator in case of conflicts between the package file and the filesystem file.
Bug
Resolved
Critical