Support all Attic/Borg command-line arguments, not just some of them #14

Closed
opened 2018-01-05 05:33:42 +00:00 by import_bot · 4 comments
Collaborator

A commonly reported type of feature request for atticmatic is to add support for a particular command-like option of Attic or Borg on the create/prune/check sub-commands that atticmatic uses. Instead of individually adding support for each requested options, or having to scramble to support new options as Attic/Borg releases come out, it might be better to just support all options.

One way to do this would be to dynamically introspect Attic/Borg command-line options, and base the atticmatic config file format on the options that Attic/Borg expect. This is a little tricky to do, because Attic/Borg don't make their command-line parser easy to get at programmatically.

Note that this would likely require a breaking config file format change, so it probably needs to be coupled with a config file upgrade tool.


Imported from Taiga issue 13 (to do). Created on 2015-09-20T02:33:08+0000 by Dan Helfman.

A commonly reported type of feature request for atticmatic is to add support for a particular command-like option of Attic or Borg on the create/prune/check sub-commands that atticmatic uses. Instead of individually adding support for each requested options, or having to scramble to support new options as Attic/Borg releases come out, it might be better to just support all options. One way to do this would be to dynamically introspect Attic/Borg command-line options, and base the atticmatic config file format on the options that Attic/Borg expect. This is a little tricky to do, because Attic/Borg don't make their command-line parser easy to get at programmatically. Note that this would likely require a breaking config file format change, so it probably needs to be coupled with a config file upgrade tool. --- Imported from Taiga issue 13 (to do). Created on 2015-09-20T02:33:08+0000 by Dan Helfman.

Yes please, this would be great to have.

Yes please, this would be great to have.

i.e. I'd like to lower the --checkpoint-interval value and I don't see a way to do so.

i.e. I'd like to lower the `--checkpoint-interval` value and I don't see a way to do so.
Owner

Since this ticket is a bigger effort, I've filed a separate ticket just for supporting --checkpoint-interval: #87. Feel free to follow it there.

Since this ticket is a bigger effort, I've filed a separate ticket just for supporting `--checkpoint-interval`: #87. Feel free to follow it there.
Owner

Closing this "won't fix" for a couple of reasons: 1. It's generally easier to add support for new options to borgmatic than it used to be. 2. I don't think any sort of automatic introspection of Borg options is a good idea or very feasible.

Having said that, I do want to encourage folks who see missing options that they'd like to use to file individual tickets for them!

Closing this "won't fix" for a couple of reasons: 1. It's generally easier to add support for new options to borgmatic than it used to be. 2. I don't think any sort of automatic introspection of Borg options is a good idea or very feasible. Having said that, I do want to encourage folks who see missing options that they'd like to use to file individual tickets for them!
Sign in to join this conversation.
No Milestone
No Assignees
3 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: borgmatic-collective/borgmatic#14
No description provided.