A previous PR (https://github.com/entropy-lab/entropy/pull/227) augmented the InProcessParamStore implementation to wrap values in instances of the Param class. This was done to enable adding bits of metadata to ParamStore values in the future. This change, however, is a breaking change in that ParamStore JSON files stored using the previous method can no longer be read by the new code.
This PR gives Entropy users a tool to automatically upgrade older ParamStore JSON files to the new format supporting Param instances. When users instantiate a new SqlAlchemy instance on an existing project they are stopped with a message asking them to upgrade.
Users can then upgrade their ParamStore JSON files by running the entropy upgrade <project dir path> CLI command. The command assumes the JSON file is present at its default location in <project dir path>/.entropy/params.json.
This PR supersedes PR https://github.com/entropy-lab/entropy/pull/233
A previous PR (https://github.com/entropy-lab/entropy/pull/227) augmented the
InProcessParamStore
implementation to wrap values in instances of theParam
class. This was done to enable adding bits of metadata toParamStore
values in the future. This change, however, is a breaking change in thatParamStore
JSON files stored using the previous method can no longer be read by the new code.This PR gives Entropy users a tool to automatically upgrade older
ParamStore
JSON files to the new format supportingParam
instances. When users instantiate a newSqlAlchemy
instance on an existing project they are stopped with a message asking them to upgrade.Users can then upgrade their
ParamStore
JSON files by running theentropy upgrade <project dir path>
CLI command. The command assumes the JSON file is present at its default location in<project dir path>/.entropy/params.json
.