Show the results of configuration file merging #673

New Issue

Closed

opened 2023-04-10 21:07:36 +00:00 by alsoeric · 4 comments

alsoeric commented 2023-04-10 21:07:36 +00:00

Copy Link

What I'm trying to do and why

During validation of a Borgmatic configuration file it would be helpful in debugging what is wrong if one could see the results of the merge and if there any errors, the result of the merge up to that error.

Steps to reproduce (if a bug)

Include (sanitized) borgmatic configuration files if applicable.

Actual behavior (if a bug)

Include (sanitized) --verbosity 2 output if applicable.

Expected behavior (if a bug)

Other notes / implementation ideas

Environment

borgmatic version: [version here]

Use sudo borgmatic --version or sudo pip show borgmatic | grep ^Version

borgmatic installation method: [e.g., Debian package, Docker container, etc.]

Borg version: [version here]

Use sudo borg --version

Python version: [version here]

Use python3 --version

Database version (if applicable): [version here]

Use psql --version or mysql --version on client and server.

operating system and version: [OS here]

#### What I'm trying to do and why During validation of a Borgmatic configuration file it would be helpful in debugging what is wrong if one could see the results of the merge and if there any errors, the result of the merge up to that error. #### Steps to reproduce (if a bug) Include (sanitized) borgmatic configuration files if applicable. #### Actual behavior (if a bug) Include (sanitized) `--verbosity 2` output if applicable. #### Expected behavior (if a bug) #### Other notes / implementation ideas #### Environment **borgmatic version:** [version here] Use `sudo borgmatic --version` or `sudo pip show borgmatic | grep ^Version` **borgmatic installation method:** [e.g., Debian package, Docker container, etc.] **Borg version:** [version here] Use `sudo borg --version` **Python version:** [version here] Use `python3 --version` **Database version (if applicable):** [version here] Use `psql --version` or `mysql --version` on client and server. **operating system and version:** [OS here]

witten commented 2023-04-10 22:06:55 +00:00

Owner

Copy Link

I appreciate you filing this. It seems like a totally reasonable user debugging tool, perhaps as part of the existing validate-borgmatic-config with an additional flag.

I appreciate you filing this. It seems like a totally reasonable user debugging tool, perhaps as part of the existing `validate-borgmatic-config` with an additional flag.

alsoeric commented 2023-04-10 23:54:06 +00:00

Author

Copy Link

yes. maybe a --verbose or --list

yes. maybe a --verbose or --list

👍 1

witten referenced this issue from a commit 2023-04-11 17:49:25 +00:00

View the results of configuration file merging via "validate-borgmatic-config --show" flag (#673).

witten commented 2023-04-11 17:50:34 +00:00

Owner

Copy Link

I went with a --show flag. This is now implemented in master and will be part of the next release. The documentation will be here shortly: https://torsion.org/borgmatic/docs/how-to/make-per-application-backups/#debugging-includes

Thanks again for the idea!

I went with a `--show` flag. This is now implemented in master and will be part of the next release. The documentation will be here shortly: https://torsion.org/borgmatic/docs/how-to/make-per-application-backups/#debugging-includes Thanks again for the idea!

witten closed this issue 2023-04-11 17:50:34 +00:00

witten commented 2023-04-13 22:19:01 +00:00

Owner

Copy Link

This has been released as part of borgmatic 1.7.12!

This has been released as part of borgmatic 1.7.12!

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

No description provided.