Enable passing parameters via env vars or a config file

[fpriyatna]

Describe the bug
Right now, the tool has to be run in interactive mode thus making it difficult to automatize the whole process and integrate it with other systems

Expected behavior
It would be nice if the parameters needed by the tool can passed via either env vars or a config file.

[daniel-dona]

I think the best option can be a config file in YAML or JSON mapping the possible interactions with the existing interface. What do you think @dachafra?

[dachafra]

and a config.ini similar to what we did for morph-kgc? It will be easier to integrate with the app as it is in python. If not, I'll be happy as well with a YAML file. @daniel-dona could yo do a draft of the file and post it here? Then we can implement it

[daniel-dona]

It can be a config.ini, at the end is the same, just a file with the same information the UI is asking the user:

• List of sizes: 1, 5, ... (1 or more)
• Distribution: JSON, XML, CSV, MongoDB, MySQL or CUSTOM (1 or more)
• For CUSTOM distribution a value for every source (AGENCY, CALENDAR_DATES...) must be provided: JSON, XML, CSV, MongoDB, MySQL (select one)

I'll try to provide a complete example next week

[dachafra]

ok, it makes sense. Let's wait for the final version of the file and then we will proceed and plan the implementation.
@daniel-dona if you think that JSON or YAML fit better than a config.ini file, go ahead ;-)