New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
enable custom config file #32
base: master
Are you sure you want to change the base?
Conversation
390dff4
to
dbd66ac
Compare
Looks good; I'll try and find some time to test this soon. Note to myself: Document this feature in readme & the default config file itself. |
Both are already included in this PR . |
Nope, with 'default config file' I meant default.zfsbud.conf, with documenting in readme, I meant 'introduction' and 'usage' part of the file. Sorry for not being clear on this. |
@kapitainsky Looking at the code, this appears to be overwriting the inline |
I will look into it. Please note I have been using all these PRs in production for many months now:) And I am very happy with my new functionality |
I'm happy you are and I am thankful for your contribution, but as the maintainer I need to be thinking in more broader terms and cover more use cases. A setting in a configuration file should not be overwriting an inline argument in my opinion. |
dbd66ac
to
4bb8099
Compare
Agree. Good catch. Fixed |
Sometimes it is useful to use different config files e.g. when different snapshots retentions are needed for different datasets. I have added "-C, --custom-config </path/to/file>" option
4bb8099
to
e40a15c
Compare
Sometimes it is useful to use different config files e.g. when different snapshots retentions are needed for different datasets.
I have added "-C, --custom-config </path/to/file>" option