You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Apr 1, 2026. It is now read-only.
It would be very useful, if Config.__load_config_file() also checked for a directory with configuration files and load them. Example:
/etc/mysoftware>/config.conf <-- Main configuration file/etc/mysoftware>/config.conf.d <-- Directory with additional configuration files extending/overriding the main configuration file/etc/mysoftware/config.conf.d/01_some_file.conf <-- File with additional configuration options./etc/mysoftware/config.conf.d/02_and_some_more.conf
The reason this would be very useful is that in a distributed environment managed with chef/salt/ansible/whatever, I could have the same base configuration file that gets installed on every server but then distribute individual files which enable certain functionality to some machines.
I would use this with the newrelic_plugin_agent to enable different plugins on different machines.
I don't think this would be difficult to implement. If I can find the time I can look into it and send a pull request but maybe someone else could do it faster.
It would be very useful, if Config.__load_config_file() also checked for a directory with configuration files and load them. Example:
The reason this would be very useful is that in a distributed environment managed with chef/salt/ansible/whatever, I could have the same base configuration file that gets installed on every server but then distribute individual files which enable certain functionality to some machines.
I would use this with the newrelic_plugin_agent to enable different plugins on different machines.
I don't think this would be difficult to implement. If I can find the time I can look into it and send a pull request but maybe someone else could do it faster.