Clarify required versus optional config values #57
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
When running
generate-borgmatic-config, the command generates a giant config file full of both optional and required configuration values. But only two of the values are actually required, and it's not the best first-time user experience to have to wade through most of the values just to end up deleting them or commenting them out.So as part of this ticket, improve that first-time experience and make it more obvious which values are required.
Implementation ideas
Idea 1:
Make it more explicit in the generated config file comments:
(Idea from Zach Coffey.)
Idea 2:
Generate the example config file with optional values commented out, so it's clear that you really just need to focus on the commented-in required values.
Idea 3:
Add a flag to
generate-borgmatic-configthat generates just the minimal config file with only the required values set.Implemented idea 2 (optional values render as commented out) in borgmatic 1.2.5.