David de la Iglesia Castro

> Is this the simplest/best way to handle custom files (not params.yaml)? My main motivation for going with `hydra.output_file` was to make it explicit, as I consider the composing and...

> @daavoo I haven't had a chance to look at your responses yet, but @dmpetrov asked why Hydra is configured in .dvc/config instead of at the pipeline/stage level inside dvc.yaml?...

> > @daavoo I haven't had a chance to look at your responses yet, but @dmpetrov asked why Hydra is configured in .dvc/config instead of at the pipeline/stage level inside...

Some ideas for enabling this at the `stage` level: - Consider `hydra` a reserved key inside `params`. If `hydra` is present in `params` of a stage, trigger the compose and...

Latest update: - `config.hydra.config_dir` is the config option that enables/disables the hydra compose and dump behavior. - By default, composed config will be dumped to `params.yaml`. `config.hydra.output_file` is now optional...

> We are only supporting a single Hydra output file, so why not use the default params file? If people don't want the path params.yaml, we can fix that in...

> Is this case correctly handled by your parameter storage? @d-miketa I think so, with proper setup. I am making some assumptions here based on what you shared (like the...

> This could lead to situations like setting only hydra.config_name and being confused about why it doesn't work. What do you think about either: > > - Making a separate...

Reopening as a Good First Issue for the UI enhancement. Would need to update https://github.com/iterative/dvc/blob/f7fbac1eed12c8e5e7b6657fd741d4f426a6fe26/dvc/exceptions.py#L132-L138 Used in https://github.com/iterative/dvc/blob/main/dvc/repo/graph.py#L27

Hi @liljenstolpe , not to dismiss the request, but is there a reason for not running `dvc install` in the original repo being added as a submodule? Anyhow, this would...