Why OpenLegacy chose a CLI for parsing legacy assets
It has a repository where you store existing assets. Users interact with the repository through a GUI used for creating services.
People ask when we have such a great-looking GUI for the Hub, why did we choose to create a CLI for parsing, testing, and pushing the assets into the Hub?
The primary reason is automation.