Feature Description
Presently, nucleus lite doesn't handle (or expect) the configuration database to be corrupt. Ideally, it should better handle unexpected errors and corruptions at startup, and in subsequent queries.
Use Case
If the database is corrupt, critical configuration parameters, such as the endpoints, might not be able to be retrieved. This will result in the device not being able to reach the cloud anymore, meaning it can no longer be remotely managed.
Proposed Solution
If corruption is detected, delete the database and recreate a base configuration from the configuration YAML files in the read-only root filesystem. That way, default endpoints can always be baked into the Linux distribution.
Feature Description
Presently, nucleus lite doesn't handle (or expect) the configuration database to be corrupt. Ideally, it should better handle unexpected errors and corruptions at startup, and in subsequent queries.
Use Case
If the database is corrupt, critical configuration parameters, such as the endpoints, might not be able to be retrieved. This will result in the device not being able to reach the cloud anymore, meaning it can no longer be remotely managed.
Proposed Solution
If corruption is detected, delete the database and recreate a base configuration from the configuration YAML files in the read-only root filesystem. That way, default endpoints can always be baked into the Linux distribution.