netdata
[Feat]: Dynamic Configuration File Creation
Problem
When a user makes a change in the UI such as adding an alert, an integration, etc, no file is created or updated in a way that a user can manage. This means that reproducing or replicating changes are all click-ops in the UI.
Description
I would propose that creating anything in the UI would create the corresponding config file or merge with the existing configuration file or something similar. This functionality already partially exists when modifying a file such as windows.conf where a template is pulled for the user and a file created.
Importance
must have
Value proposition
- This would allow us to backup any changes made
- This would allow us to better leverage automation to ensure that files are being kept up to date in our code repos and any changes via the UI committed and reviewed just in case.
- This would also allow us to open up the UI permissions to others who may not code but need to get an alert or other feature setup.
Proposed implementation
Like with the template conf files, when a UI config change is made, create a conf file to match in the path where a user would manually add a config. Merging is likely a bit harder especially combining a user created and a ui change made. However UI changes into an existing UI created file I would hope would be easier.
