Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support configuration scopes #1725

Closed
vkarak opened this issue Feb 1, 2021 · 1 comment · Fixed by #2557
Closed

Support configuration scopes #1725

vkarak opened this issue Feb 1, 2021 · 1 comment · Fixed by #2557

Comments

@vkarak
Copy link
Contributor

vkarak commented Feb 1, 2021

Quoting from @akesandgren:

It would be somewhat more user friendly if it augmented the settings.py from the user with the core/settings.py. Although I would prefer if it did read and augment config files in the order -C, $HOME/..., the other ones from "Locating the Configuration File", core/settings.py.
Or perhaps one should do it the other way around and override with whatever values comes from the read file, i.e. read core/settings.py, XDG_DATA/reframe.d/settings.py, $HOME/... (also using the XDG_USER style), and finally any -C config files.

I'm not entirely sure about chaining the -C option, but I'm totally in favor of supporting configuration scopes, so that you only redefine the relevant parts of the documentation.

@akesandgren
Copy link
Contributor

I was thinking of a -C file1:file2:file3 which would be the same as reading from the other files above.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
3 participants