Subdirectory Configuration Scheme

[hedinasr]

Should we use the Subdirectory Configuration Scheme instead of a single configuration file ? The documentation says that it is a better practice, so, do you think that we can refactor the module ?

[thbe]

How is this linked together? Is e.g. /etc/bareos/bareos-dir.d/ sufficient to contain all configuration or is there still the requirement to link the configuration items in the bareos-dir.conf like we do it currently? In principle I like the idea to use subdirectory for the configuration instead of a single big file. On the other hand you need to ensure that only Puppet is in control of that directory because otherwise the service might stop if you do an upgrade which put new files in this directory (for whatever reason) ...

[hedinasr]

The /etc/bareos/bareos-dir.d/ directory is enough to manage Bareos. For example, if you need to add a new backup job, you just need to create a new job file in /etc/bareos/bareos-dir.d/job/.
If files are added in this directory, I think that we could notify the service bareos-dir when a change become in /etc/bareos/bareos-dir.d/.

[thbe]

Sounds good! I‘m currently a little bit short on time, but I try to refactor the module within the next two or three weeks.