add a way to bootstrap config

Carey Black  3 hours ago
Actually let me be a bit more specific and only talk about the SMTP external system registration/config for a moment. ( As an example of what I think @jasonrap is generally asking about. )
grouper.base.properties has a set of properties "mail.smtp.*" that allow you to deliver a file to the image that could configure the SMTP external system. However, it is a fairly special case. I don't know of anyone who would have more than one SMTP external system. But I guess it could happen?!?
Is there a generic way to do that kind of "bootstrapping configuration" with any external system?
Also I kind of thought the general direction was to "not use files to drive the configuration" at this point and instead push as much of it as possible into the DB?
Maybe there should be a generic way to register any external system so that it is loaded into the DB config?
Maybe a "on startup execute a directory of GSH files" ?
Maybe a way to "load a set of files into the DB" at container startup?
Maybe a way to execute "start script files from the DB" on Daemon startup?
This way programmatically the files could "add if not present" and "back off" if already defined, or keep stomping on the config and use the file to drive it. Their choice.
As well as not be limited to the current fixed java properties keys/files structure.
And the deployer would not need to do "anything special" on startup to get a new provisioner added. Update the file ( a copy/paste/tweak from a lower environment) and redeploy the service.
The same bootstrap topic applies to every other configuration setting too. ( Well, except for the DB and it's credentials. :slightly_smiling_face: )
REFs  in Jiras ? :
https://todos.internet2.edu/browse/GRP-3343
https://todos.internet2.edu/browse/GRP-3398
https://todos.internet2.edu/browse/GRP-3442 (edited)