Auto comment or uncomment sections based in projects.json

[jsmanrique]

Reading projects.json it is possible to know which data sources (backends) are gonna be requested and which ones not. Even further, it's possible to know which indexes are gonna be generated and which ones not.

Wouldn't it be nice if setup.cfg backends sections could be built based in the backends listed in the projects.json without needing initial human intervention to comment or uncomment sections?

[valeriocos]

Thank you @jsmanrique for sharing this idea. It looks interesting and it could be implemented as a script that takes as input a projects.json and generates a setup.cfg. The latter will set default values for some sections (e.g., sortinghat, raw and enrichment), while it will automatically define other ones (e.g., name of raw, enriched and study indexes) for backend sections.
WRT commenting/uncommenting backend sections, a procedure in the same script or in a new one could be defined to validate a setup.cfg against a projects.json.
If you agree, we can try to list a set of requirements and push this forward, WDYT?

[jsmanrique]

LGTM