I'm more of an avaje-config guy myself, so I think it would be good if we could generalize the configuration to make it a CYOA and not tie it to any one implementation.

Just for reference this was discussed earlier here: #1712 (comment)

(scroll for responses).

The issue is as I believe @jknack expressed is that all the optional modules expect Lightbend Config both from a Java interface contract but also perhaps more importantly documented configuration format.

I hate to denigrate Microprofile but tried my best to be involved with Microprofile Config in hopes it could fill the niche for a config facade but that community seems to be very closed off (I am actually a little jaded about that and reminds me of old school design by committee that new Microprofile JEE was supposed to resolve...). BTW Microprofile Config is still not a Java module so it is for sure off the table.

That being said I'm still in favor of a config abstraction for pluggable config.