I'd like to to use git to start managing our Bacula configuration files, but want to keep out (or mask) the passwords in these files.
- looked for a setting within Bacula that allows pointing to a keyfile(s) instead of a password. It seems this would entail moving to the SSL setup
- using the git "clean" and "smudge" filters. It seems like that would require patching the passwords back in manually though, or writing some custom logic for the "smudge" operation
- Using the "include other files" directive. But the lines I want to exclude are scattered throughout the config file
Is there an easier way that I've overlooked?