borgmatic-collective/borgmatic
borgmatic-collective
/
borgmatic
15
57
Fork 40
Code Issues 53 Pull Requests 1 Actions Packages Releases 121 Activity

Run arbitrary Borg commands #425

New Issue
Closed
opened 2021-06-14 22:59:35 +00:00 by witten · 3 comments
witten commented 2021-06-14 22:59:35 +00:00
Owner
Copy Link

What I'm trying to do and why

An oft-mentioned feature request is the ability for borgmatic to run Borg commands with arbitrary arguments.

The "why" is that borgmatic actions do not currently wrap all current or future Borg commands/options. (See #394 for an example.) So sometimes it would be nice to drop down to running Borg (nearly) directly while still making use of all the niceties of borgmatic's configuration with repositories, SSH settings, etc.

Proposed design

There could be a new "borg" action something like this:

borgmatic -c config.yaml -v 2 borg break-lock

Which would run a borg command like:

borg break-lock --debug --show-rc test.borg

Whereas this:

borgmatic -v 2 -c test.yaml borg --archive test list

Would run a borg command like:

borg list --debug --show-rc test.borg::test

Unlike all other borgmatic actions that can share options, this action would work by "greedily" consuming any Borg arguments following "borg" and not share them with other borgmatic actions. Global borgmatic options could still go before the "borg" action.

When running the given Borg command, repository name (and archive name, where applicable) would be constructed entirely by borgmatic to take advantage of its repositories listed in configuration. This means that repository/archive names should not be specified as part of the supplied Borg options.

Help for the new action might look something like this:

usage: borgmatic borg [--repository REPOSITORY] [--archive ARCHIVE] [OPTION [OPTION ...]] [-h]

Run an arbitrary Borg command based on borgmatic's configuration

borg arguments:
  --repository REPOSITORY
                        Path of repository to pass to Borg, defaults to the configured repositories
  --archive ARCHIVE     Name of archive to pass to Borg (or "latest")
  OPTION [OPTION ...]   Options to pass to Borg
  -h, --help            Show this help message and exit
#### What I'm trying to do and why An oft-mentioned feature request is the ability for borgmatic to run Borg commands with arbitrary arguments. The "why" is that borgmatic actions do not currently wrap all current or future Borg commands/options. (See #394 for an example.) So sometimes it would be nice to drop down to running Borg (nearly) directly while still making use of all the niceties of borgmatic's configuration with repositories, SSH settings, etc. #### Proposed design There could be a new "borg" action something like this: ```bash borgmatic -c config.yaml -v 2 borg break-lock ``` Which would run a borg command like: ```bash borg break-lock --debug --show-rc test.borg ``` Whereas this: ```bash borgmatic -v 2 -c test.yaml borg --archive test list ``` Would run a borg command like: ```bash borg list --debug --show-rc test.borg::test ``` Unlike all other borgmatic actions that can share options, this action would work by "greedily" consuming any Borg arguments following "borg" and not share them with other borgmatic actions. Global borgmatic options could still go before the "borg" action. When running the given Borg command, repository name (and archive name, where applicable) would be constructed entirely by borgmatic to take advantage of its `repositories` listed in configuration. This means that repository/archive names should not be specified as part of the supplied Borg options. Help for the new action might look something like this: ``` usage: borgmatic borg [--repository REPOSITORY] [--archive ARCHIVE] [OPTION [OPTION ...]] [-h] Run an arbitrary Borg command based on borgmatic's configuration borg arguments: --repository REPOSITORY Path of repository to pass to Borg, defaults to the configured repositories --archive ARCHIVE Name of archive to pass to Borg (or "latest") OPTION [OPTION ...] Options to pass to Borg -h, --help Show this help message and exit ```
witten added the
design finalized
 label 2021-06-14 23:01:20 +00:00
witten commented 2021-06-18 03:53:56 +00:00
Author
Owner
Copy Link

Released in borgmatic 1.5.15! Docs here: https://torsion.org/borgmatic/docs/how-to/run-arbitrary-borg-commands/

Released in borgmatic 1.5.15! Docs here: https://torsion.org/borgmatic/docs/how-to/run-arbitrary-borg-commands/
Ghost commented 2021-06-18 04:29:06 +00:00
Copy Link

thank you very very much, thos will save me a lot of time. ☺

thank you very very much, thos will save me a lot of time. ☺
witten commented 2021-06-18 04:48:14 +00:00
Author
Owner
Copy Link

I'm so glad to hear it! Since there are several limitations with the new action (see the docs), please let me know if any of them prove problematic for your use cases. I wanted to optimize for speed rather than "perfect".

I'm so glad to hear it! Since there are several limitations with the new action (see the docs), please let me know if any of them prove problematic for your use cases. I wanted to optimize for speed rather than "perfect".
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
main
spot-check
1.8.10
1.8.9
1.8.8
1.8.7
1.8.6
1.8.5
1.8.4
1.8.3
1.8.2
1.8.1
1.8.0
1.7.15
1.7.14
1.7.13
1.7.12
1.7.11
1.7.10
1.7.9
1.7.8
1.7.7
1.7.6
1.7.5
1.7.4
1.7.3
1.7.2
1.7.1
1.7.0
1.6.6
1.6.5
1.6.4
1.6.3
1.6.2
1.6.1
1.6.0
1.5.24
1.5.23
1.5.22
1.5.21
1.5.20
1.5.19
1.5.18
1.5.17
1.5.16
1.5.15
1.5.14
1.5.13
1.5.12
1.5.11
1.5.10
1.5.9
1.5.8
1.5.7
1.5.7.dev0
1.5.6
1.5.5
1.5.4
1.5.3
1.5.2
1.5.1
1.5.0
1.4.22
1.4.21
1.4.20
1.4.19
1.4.18
1.4.17
1.4.16
1.4.15
1.4.14
1.4.13
1.4.12
1.4.11
1.4.10
1.4.9
1.4.8
1.4.7
1.4.6
1.4.5
1.4.4
1.4.3
1.4.2
1.4.1
1.4.0
1.3.26
1.3.25
1.3.24
1.3.23
1.3.22
1.3.21
1.3.20
1.3.19
1.3.18
1.3.17
1.3.16
1.3.15
1.3.14
1.3.13
1.3.12
1.3.11
1.3.10
1.3.9
1.3.8
1.3.7
1.3.6
1.3.5
1.3.4
1.3.3
1.3.2
1.3.1
1.3.0
1.2.18
1.2.17
1.2.16
1.2.15
1.2.14
1.2.13
1.2.12
1.2.11
1.2.10
1.2.9
1.2.8
1.2.7
1.2.6
1.2.5
1.2.4
1.2.3
1.2.2
1.2.1
1.2.0
1.1.15
1.1.14
1.1.13
1.1.12
1.1.11
1.1.10
1.1.9
1.1.7
1.1.6
1.1.5
1.1.4
1.1.3
1.1.2
1.1.1
1.1.0
1.0.3
1.0.2
1.0.1
1.0.0
0.1.8
0.1.7
0.1.6
0.1.5
0.1.4
0.1.3
0.1.2
0.1.1
0.1.0
0.0.7
0.0.6
0.0.5
0.0.4
0.0.3
0.0.2
Labels
Clear labels   
bug

   
data loss

   
design finalized

   
good first issue

   
new feature area

   
question / support

   
security

   
waiting for response
No Label
bug
data loss
design finalized
good first issue
new feature area
question / support
security
waiting for response
Milestone
Clear milestone
No items
No Milestone
Assignees
Clear assignees
No Assignees
2 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#425
No description provided.
Delete Branch "%!s(<nil>)"

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?