I think it would be best to keep the addons configuration in addons.yaml.
With the present proposal the addons to use for a repository can be configured in two ways. Either with an extra key restrict_modules in repos.yaml, or by listing them under the repo name in addons.yaml.
The disadvantage IMHO is that we introduce a new kind of key in repos.yaml. Even though that is supported, it seems out of place. Also it seems better to me to have one way to do things.
I tested this solution both with no addons.yaml at all and with addons.yaml just containing:
I think it would be best to keep the addons configuration in addons.yaml.
With the present proposal the addons to use for a repository can be configured in two ways. Either with an extra key restrict_modules in repos.yaml, or by listing them under the repo name in addons.yaml.
The disadvantage IMHO is that we introduce a new kind of key in repos.yaml. Even though that is supported, it seems out of place. Also it seems better to me to have one way to do things.
I tested this solution both with no addons.yaml at all and with addons.yaml just containing: