Skip to content

Support versioning of backed up properties #80

Open
@VigneshVSV

Description

@VigneshVSV

There are certain settings in hardware which are helpful to be backed up to databases as the hardware "forgets" the setting when power cycled. It may also go to a default setting. This may also happen accidentally when restarting the Thing especially when the device driver is re-initialized.

Since settings are generally modelled as properties, after the property write, the value can be stored to the database.
We also support JSON files to be used in place of actual databases (In this case the db_engine value of Thing points to a file descriptor of JSON file)

As a further extension of this JSON based storage, we want to "version" this backup so that settings history can be tracked in time.
Moreover, for running experiment scans, it useful to be able to fetch and populate new settings in every run of the loop.

There is an experimental implementation of a tool which helps with this: corev

The workflow is to be described as follows:

  • upcoming

Metadata

Metadata

Assignees

No one assigned

    Labels

    draftthis issue is in draft state and is not be ready for working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions