Let generate-borgmatic-config override existing files. #539

New Issue

Closed

opened 2022-05-29 13:59:58 +00:00 by ams_tschoening · 2 comments

ams_tschoening commented 2022-05-29 13:59:58 +00:00

Copy Link

What I'm trying to do and why

I maintain all my YAML configs using SVN and after upgrading BorgMatic to 1.6.1, tried the process of generate-borgmatic-config for the first time. The important thign to note is that I really checkout those configs at the server backing things up as well. So for my workflow there's not really the need to force users to upgrade the configs into an additional file, but instead make things more difficult:

If overwriting the source file would be possible, I could use svn diff either on the server or simply after downloading the whole file tree e.g. using pscp to my client with support for GUI to modify new configs according to my needs. With additional files in place, I need to rename or delete or copy more than necessary.

Other notes / implementation ideas

Maybe some --force option would be enough already to prevent the check for an existing file. Or maybe optionally output destination contents to STDOUT, so one can redirect using the shell into the source file.

Thanks!

Environment

borgmatic version: 1.5.24
borgmatic installation method: PIP, system wide
Borg version: 1.1.16
Python version: 3.8.10
operating system and version: Ubuntu 20.04

#### What I'm trying to do and why I maintain all my YAML configs using SVN and after upgrading BorgMatic to 1.6.1, tried the process of `generate-borgmatic-config` for the first time. The important thign to note is that I really checkout those configs at the server backing things up as well. So for my workflow there's not really the need to force users to upgrade the configs into an additional file, but instead make things more difficult: If overwriting the source file would be possible, I could use `svn diff` either on the server or simply after downloading the whole file tree e.g. using `pscp` to my client with support for GUI to modify new configs according to my needs. With additional files in place, I need to rename or delete or copy more than necessary. #### Other notes / implementation ideas Maybe some `--force` option would be enough already to prevent the check for an existing file. Or maybe optionally output destination contents to STDOUT, so one can redirect using the shell into the source file. Thanks! #### Environment **borgmatic version:** 1.5.24 **borgmatic installation method:** PIP, system wide **Borg version:** 1.1.16 **Python version:** 3.8.10 **operating system and version:** Ubuntu 20.04

witten referenced this issue from a commit 2022-05-29 23:04:09 +00:00

Add "generate-borgmatic-config --overwrite" flag to replace an existing destination file (#539).

witten commented 2022-05-29 23:05:01 +00:00

Owner

Copy Link

I've implemented this in master with a new "--overwrite" flag. It'll be part of the next release. Thanks for the suggestion!

I've implemented this in master with a new "--overwrite" flag. It'll be part of the next release. Thanks for the suggestion!

👍 1

witten closed this issue 2022-05-29 23:05:01 +00:00

witten commented 2022-05-31 16:45:27 +00:00

Owner

Copy Link

This has been released in borgmatic 1.6.2!

This has been released in borgmatic 1.6.2!

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

No description provided.