Page History

...

cpo proposal:
- one script (configdb_modify.py) that reads the configdb json, modifies it (with python code)
  and writes it back (a plug or a minus: we no longer have a script that knows the official
  state of the schema: the database itself is the source of truth).
  - if we ever lost the database we no longer know the configdb schemas

Another proposal (from Ric):

• Change the *_config_store.py scripts to take another command line argument that selects between creating a new configdb entry or modifying an existing one
  • If creating, behave as now
  • if modifying:
    • read the configdb entry into a json string
    • apply the modified schema coded elsewhere in *config_store.py to configdb
    • use the json string from above to update the values of the new configdb entry
      • elements that are in the configdb entry but not in the json string are ignored
      • elements that are not in the configdb entry but are in the json string are ignored
• The RO elements like help and version numbers should be governed by the new schema code and not by the previous DB contents

item 1:

ts_config_V1:
config[group][0][rate]=10Hz
             [1][rate]=100Hz
             [2][rate]=100Hz

...