User Override Through Additional Config

[shfattig]

I'm having a lot of trouble using hydra inside an installable library. I want to provide default configuration but ultimately allow a user (an application) the final ability to tweak their configuration. I understand the reasons behind the design decisions, but my use case is inhibited by the relative path of the search path and the limited overrideability of configs. I found a few workarounds based on other users' attempts to do something similar, but all include some kind of hack that I'd rather avoid.

This stack overflow question looks to be attempting my exact use case, and expresses well the same frustrations I've encountered. Omry responded over two years ago acknowledging the holes in hydra for this use case, but not knowing whether another discussion was opened for it I decided to make one myself! Any solutions or progress toward this functionality?

Hydra is super cool and provides some amazing advantages for my library, as long as I can get this issue resolved!