disable subject source via env var (via config)

Carey Black
7:16 PM
I spent some time with Tim Maness.
Setting up subject source (in the DB, via the UI) can be a 'opps now the container will not start. Now what?' problem.
Maybe there should be a container flag, or a CLI to do the following:
Export all subject config to a file and delete the config from the grouper_config table.
It can be very frustrating when you break the container by using the UI.

Chad Redman
7:58 PM
that's true, you can't even use gsh because it will exit if it can't boot all its subject sources

Carey Black
8:37 PM
I guess another alternative would be to disable a subject source before startup via an ENV setting?
DISABLED_SUBJECT_SOURCES=sub_one_source;sub_two_source;
Then ( somehow ) during start up honor the ENV value by "skipping" those subject sources like they don't exist yet?

Chris: note, it should be a subject.properties config that defaults to env var...