Document or implement custom ssh command when extracting the configuration files used to create an archive (bootstrap) #767

New Issue

Closed

opened 2023-10-05 13:58:50 +00:00 by moanos · 4 comments

moanos commented 2023-10-05 13:58:50 +00:00

Copy Link

What I'd like to do and why

I'd like to extract the configuration file from a repo. That repo is accessed via SSH with public key. Therefore also need to adjust the SSH command to extract the file. I think there is no option to do that yet, if there is it would be nice to document this here.

For reference: I create my backups with something like this on server A

repositories:
- path: ssh://backupuser@backupserver.example.org/./backup/reponame
source_directories:
- /mash
ssh_command: ssh -o "StrictHostKeyChecking accept-new" -i /etc/borgmatic.d/sshkey

and try to do this on server B

borgmatic config bootstrap --repository ssh://backupuser@backupserver.example.org/./backup/reponame --destination /tmp --ssh-command "ssh -i mykey"

Other notes / implementation ideas

No response

### What I'd like to do and why I'd like to extract the configuration file from a repo. That repo is accessed via SSH with public key. Therefore also need to adjust the SSH command to extract the file. I think there is no option to do that yet, if there is it would be nice to document this [here](https://torsion.org/borgmatic/docs/how-to/extract-a-backup/#extract-the-configuration-files-used-to-create-an-archive). For reference: I create my backups with something like this on server A ```yml repositories: - path: ssh://backupuser@backupserver.example.org/./backup/reponame source_directories: - /mash ssh_command: ssh -o "StrictHostKeyChecking accept-new" -i /etc/borgmatic.d/sshkey ``` and try to do this on server B ```zsh borgmatic config bootstrap --repository ssh://backupuser@backupserver.example.org/./backup/reponame --destination /tmp --ssh-command "ssh -i mykey" ``` ### Other notes / implementation ideas _No response_

moanos commented 2023-10-05 14:07:42 +00:00

Author

Copy Link

I just realized I can do export BORG_RSH="ssh -i /root/mykey" so it would be nice to document that

I just realized I can do `export BORG_RSH="ssh -i /root/mykey"` so it would be nice to document that

witten commented 2023-10-05 16:20:26 +00:00

Owner

Copy Link

Good find, yeah! I was just about to suggest that as a work-around. However I think this is a feature that should probably be built into the bootstrap action as well, maybe via a --ssh-command flag as you suggest. So I'll add that as part of this ticket and at least mention it in the documentation. Thanks for filing this!

Good find, yeah! I was just about to suggest that as a work-around. However I think this is a feature that should probably be built into the `bootstrap` action as well, maybe via a `--ssh-command` flag as you suggest. So I'll add that as part of this ticket and at least mention it in the documentation. Thanks for filing this!

❤️ 1

witten referenced this issue from a commit 2023-12-24 18:35:00 +00:00

Add an "--ssh-command" flag to the "config bootstrap" action (#767).

witten commented 2023-12-24 18:36:15 +00:00

Owner

Copy Link

config bootstrap --ssh-command has been implemented in main and will be part of the next release. Thanks again for the suggestion!

`config bootstrap --ssh-command` has been implemented in main and will be part of the next release. Thanks again for the suggestion!

witten closed this issue 2023-12-24 18:36:15 +00:00

witten commented 2024-01-03 18:12:09 +00:00

Owner

Copy Link

Released in borgmatic 1.8.6!

Released in borgmatic 1.8.6!

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

Subscribe

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#767

No description provided.