Hydra search path plugin organizatoin

[relativistic]

We have a situation where we have a central hydra-powered command line application. We want to provide separate python packages that provide new configs. The hydra_search_path plugin seems ideal to automatically add new configs to the hydra search path in the python virtual environment.

Now, one thing that is interesting about the hydra search path plugin is, as far as I can tell, all hydra applications will be able to see these new search paths, even if they do not apply. Is there any way to avoid this? Some kind of "namespace" system. Or to have a filter app filter which configs provided by search path plugins it will consider?

I notice that ConfigSearchPath.append takes a provider and an anchor argument. I can't find documentation on how these are used. Is it possible to use these to filter which search paths your app includes?

I could put in a feature request to hydra, but I wanted to make sure I wasn't missing an existing feature or strategy, so this seemed like a more appropriate forum.

Thanks!