Temporary Sensor Metadata Architecture is Problematic
We have been temporarily archiving sensor metadata within /geomagio/metadata/Metadata.py
with the goal of moving it into a proper database at some point in the future. However, this temporary solution requires us to go through a full Geomag-Algorithms version release every time we update. This A.) Greatly slows down and complicates the process of updating sensor metadata and B.) Increases the risk of pushing breaking changes to production since the developer sometimes has to rush the release process to support those in the field while including any and all other unrelated changes that have been committed since the previous release.
I propose that we change this temporary solution:
- Move the metadata objects within Metadata.py to file within a separate repo.
- Clone this new temporary repo to mage1 and mage2.
- Update the
get_instrument
function in Metadata.py to call the data from this repo.
This change will probably require manual git pull
calls whenever metadata is updated, and I assume that we will want to use a Linux environment variable to point to the local location of the files. But to me this process seems easier and less messy than what we currently have. Are there any potential issues with Typer apps using code that reference external files?