[Feature Request] Add `overrides` parameter to `@hydra.main()`

[addisonklinke]

🚀 Feature Request

Similar to the existing config_path and config_name parameters, add an overrides keyword argument to @hydra.main to allow hydra.main to accept either a

1. Path to overrides.yaml serialized from a previous Hydra run
2. ListConfig object

There should also be a corresponding --overrides CLI flag included with the Hydra-specific options

Motivation

Is your feature request related to a problem? Please describe.

Several use-cases currently require hacking sys.argv to provide overrides in a hydra.main() context. This isn't very safe or clean from a code quality perspective

• Reproducing a Hydra run from previous Hydra job configs #1805 (comment)
• Append new fields to primary YAML config by default #2457

[Jasha10]

Thanks @addisonklinke!

[addisonklinke]

@Jasha10 I've looking at integrating Hydra for a new work project and revisiting some of these old threads. Looks like the project has somewhat gone into maintenance mode? The last release is almost 2 years old

[Jasha10]

Hi @addisonklinke, I'm no longer working at Meta.
I believe there are some folks at Meta who are making use of Hydra (and you can look at the most recently merged PRs to see who that is), but my understanding is that there's no full time team dedicated to Hydra at the moment. Rather, I suspect that users at Meta have been making updates to Hydra when doing so benefits their internal use cases. So "maintenance mode" is one way to look at it, or another could be to say that Hydra's current caretakers are less able to respond to requests coming from outside of Meta.

[Sanjay-Ganeshan]

Hi there! We're still using and evolving hydra for internal use cases.

If there's something you think will benefit the community, feel free to submit a pull request, and we will take a look at it. However, we don't have a fixed OSS release / feature request schedule.

If there's a critical feature from the hydra updates that you think is relevant to release, let us know, and I'll see what we can do about it!

[addisonklinke]

Thanks for the reply @Jasha10, best of luck with your new work and thanks for all the effort here on Hydra!

@Sanjay-Ganeshan good to know, I appreciate the insight. My current needs are mostly fulfilled, more so curious whether it would still be a good idea to rely on Hydra for new projects - sounds like that's no problem. Ideally I'd like to add PRs for this (and other) feature requests, but honestly am not sure when I'll have the bandwidth. Maybe if my team adopts it, I can gather a bit of work hours to upstream features that would benefit us

[timkpaine]

This is fixed in lerna