Details
-
New Feature
-
Resolution: Unresolved
-
Major
-
None
-
None
-
None
-
None
Description
If
the grouper DB could hold all customization's to a grouper instance in it's DB.
AND
Just before INITIAL startup of the JVM is spun up could connect to the DB. Extract the customization and "refresh" the local filesystem with the contents from the DB.
then
the setup/customization's/maintenance of the image would become be greatly reduced for deployers. ( since all the data/files are in the DB instead of the image. )
Off the top of my head I can think of these items as examples:
- CSS file(s)
- custom image(s)
- custom JS file(s)
- custom jar file(s) (for hooks/CLC/etc...)
- log4j.properties
- configs to enable/disable hooks
Also ( maybe ) the ability to reset a local auth password ( from the DB config data) on startup could be useful too. ( Thinking about that one special "when everything else can't login" account....)
There likely need to be a way to "skip this step" on INITIAL container startup too.
To avoid a "death spiral" due to some DB content that breaks the startup process entirely.