Pass through all options (that make sense) to wrapped borg commands #193
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?
There are a number of optinons the borg commands that are wrapped support, that are not passed though.
Some may not make sense, as being handled by the config, but those that do, should be possible to specify.
Examples would be
--short' and '--last' for the--listcommand.borg listsupports them, butborgmatic --list` does not.I've generally been implementing these on an as-needed / as-issue-filed basis rather than trying to go for a comprehensive full-coverage sweep. (See witten/borgmatic#14 for more info.)
Do you have more in mind besides
--list's--shortand--last?Some in mind, others I will only find out over time using borgmatic more, but each time there would be the turnaround time between ticket and release and yet more till one's distro ships that release or the extra effort of bulding a newer package yoruself (I did that now to try borgmatic, but in the long run, it should just be usable with a stable distro release).
AS for
list, there's--prefixand--format, forcreatethere may be--noatime, which I didn't make my mind up over yet.Correction: While
--noatimeis indeed missing, it rather is something that should be a config option.Done and released with borgmatic 1.3.11. I implemented pass-throughs for all list-specific flags, all info-specific flags, and I added a couple of new config file options like
atimein the location section. There still may be the odd flag here or there that needs coverage (especially withcreate), so please feel free to file follow-up tickets.I did do some investment in making it easier to add these in the future. And I should note that having real sub-commands did make this go more smoothly!