🌳🍟 ↝ Microservice for populating planet lightcurves [ GP-13 ]

[Gizmotronn]

When planets & other anomalies are created, we need to populate them with data and visual assets (the latter of which can be done using AI generators or python scripts for now). Obviously we still need to determine a pattern for how the anomalies and anomaly types are going to be organised (tables/collections & versions/generations - e.g. basePlanets table and planetsss table), so for now I’ll just have it that the planet datasets are loaded in manually each time from a flask wrapper/microservice initially. We can then link it up with the generation section from the “admin” part of our site when we want to create new collections/content.

https://signalk.atlassian.net/browse/GP-13

[height]

Link Height tasks by mentioning a task ID in the pull request title or commit messages, or description and comments with the keyword link (e.g. "Link T-123").

💡Tip: You can also use "Close T-X" to automatically close a task when the pull request is merged.

[Gizmotronn]

Build quality & code coverage will be documented in #14