Managed Assets outside of the generator - server project

[cmoulliard]

The generator project contains 2 types of assets which are needed/used to populate the zip file

1. config.yaml

When the pom.xml file is created from the pom.xml template, a for loop will add GAVs dependencies according to the list of -d passed as parameters to the URL request

2. template

The pkg/template/tmpl folder contains the different templates that we propose when a project is scaffolded: simple, rest, crud, ... if you pass as parameter - -t

Such assets are packaged within this project but we could imagine to move them under a separate github project where they will be maintained separately and will be accessed by the server at runtime ? In this case, we could release the server - generator independently of the assets.

WDYT @lincolnthree @metacosm @iocanel @geoand ?

[geoand]

I think it's a good idea - decouples deployment of the server from the templates which can then change without having to change anything in the server.

We would probably need to add some kind of syncing/caching process that would pull the templates periodically

[cmoulliard]

config is now managed as a ConfigMap mounted within the directory /etc/conf of the pod