We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
For auditing and visibility reasons we would like to keep most of the RSE settings in a git repository and have relevant access controls over them.
It would be expected from site admins and operators to write a meaningful commit / or a PR message for the change they are making.
I envision a config directory structure of the format
my-site/ ├── base-config.yaml ├── production ├── _test.yaml └── _temp.yaml └── integration ├── _test.yaml └── _temp.yaml
Where the _test and _temp configs would be applied as patches to the base config.
_test
_temp
This would help site admins take basic control of the rses without operator involvement.
Write a sync daemon for the rse settings
No response
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Enhancement Description
For auditing and visibility reasons we would like to keep most of the RSE settings in a git repository and have relevant access controls over them.
It would be expected from site admins and operators to write a meaningful commit / or a PR message for the change they are making.
I envision a config directory structure of the format
Where the
_test
and_temp
configs would be applied as patches to the base config.Use Case
This would help site admins take basic control of the rses without operator involvement.
Possible Solution
Write a sync daemon for the rse settings
Related Issues
No response
The text was updated successfully, but these errors were encountered: