Closed atemate closed 3 years ago
Hi @yartem !
it seems like recursive defaults (WIP PR here, Design Doc here) is what are you asking for.
The feature is planned for Hydra 1.1 Please feel free to check out the PR and try it (I believe it's ready for dogfooding now :) )
Yup, I believe the use case you are after is covered well by the new recursive defaults. It's getting ready to hit master, but as Jieru said it's in good enough shape for you to play with it from #1170).
I am going to close this, but feel free to continue the discussion here.
By the way, I am always happy to see new use cases for Hydra! thanks for sharing!
π Feature Request
Hi! First of all, thanks for such a simple yet functional instrument! :heart: At my work, I am doing MLOps, where I need to run multiple codebases in different environments (docker images) with different parameters (say, version of code and model), and I find hydra to fit this use-case very easily!
But one feature I really lack: the possibility to share a common configuration via importing a config file in other config files. This common config file can contain a similar tree structure that can be used in other configs, for example:
Now, I need to hack (wrap with my own code)
@hydra.main
to achieve this.