In Hydra 1.0, when config file is loaded, if a config with a matching name and group is present in the
it is used as the schema for the newly loaded config.
There are several problems with this approach:
- Inflexible: This approach can only be used when a schema should validate a single config file. It does not work if you want to use the same schema to validate multiple config files.
- Surprising: This hidden behavior can be surprising. There is no way to tell this is going to happen when looking at a given config file.
Hydra 1.1 deprecates this behavior in favor of an explicit config extension via the Defaults List.
This upgrade page aims to provide the TLDR. It is highly recommended that you read the following pages:
The migration involves two steps for each config file.
- Store use a different name when storing the schema into the config store. Common choices:
- Add the schema to the Defaults List in the config file.