The default InclExcl files (at least for Red Hat) are too aggressive for my use case. For example, I mount GPFS file systems under /mnt that do need to be backed up. Unfortunately, the excludes are hard-coded into the file https://github.com/nosolutions/puppet-tsm/blob/master/files/InclExcl.redhat#L10 and there's no way to 'undo' the exclude programatically.
I recommend pulling the values out of the static file and creating an array that is then dumped into Inclexcl file.
Another example of being too aggressive is exclude /var/log/.../*. I would think that most certainly you'd want to back up your system logs.
I understand that one can point inclexcl_source to a different, static file on the puppet server but this seems like a bit of extra work when all you really should have to do is specify an array in hiera. The module makes assumptions that aren't programmatically changeable.
The default InclExcl files (at least for Red Hat) are too aggressive for my use case. For example, I mount GPFS file systems under /mnt that do need to be backed up. Unfortunately, the excludes are hard-coded into the file https://github.com/nosolutions/puppet-tsm/blob/master/files/InclExcl.redhat#L10 and there's no way to 'undo' the exclude programatically.
I recommend pulling the values out of the static file and creating an array that is then dumped into Inclexcl file.
Another example of being too aggressive is
exclude /var/log/.../*. I would think that most certainly you'd want to back up your system logs.I understand that one can point inclexcl_source to a different, static file on the puppet server but this seems like a bit of extra work when all you really should have to do is specify an array in hiera. The module makes assumptions that aren't programmatically changeable.