bootstrap action ignores "--verbosity" when no configuration is present #1336

New issue

Closed

opened 2026-07-23 17:18:30 +00:00 by witten · 2 comments

witten commented 2026-07-23 17:18:30 +00:00

Owner

Copy link

What I'm trying to do and why

Due to its expected use case of being run on a fresh system before borgmatic is set up yet, the bootstrap action does not expect borgmatic configuration. However, due to a quirk in the way that command-line arguments override configuration file options, if you run bootstrap with a --verbosity flag, then bootstrap ignores that value unless you also provide a configuration file, e.g. with --config.

Steps to reproduce

$ borgmatic -v 2 config bootstrap --repository test.borg

Actual behavior

summary:
Bootstrap successful

(Note the lack of debug logs.)

Expected behavior

BORG_EXIT_CODES=*** borg --version --log-json --debug --show-rc
BORG_RELOCATED_REPO_ACCESS_IS_OK=*** BORG_EXIT_CODES=*** borg info --remote-path borg --log-json --glob-archives {hostname}-* --json test.borg
BORG_RELOCATED_REPO_ACCESS_IS_OK=*** BORG_EXIT_CODES=*** borg list --remote-path borg --log-json --glob-archives {hostname}-* --last 1 --json test.borg
Latest archive is flux-2026-07-20T18:59:25.829646 (3ad16973e49b6c5614c000b4c642e4cc8e7c997e24897b124ea45f011874d0b7)
Using runtime directory /run/user/1000/borgmatic
BORG_RELOCATED_REPO_ACCESS_IS_OK=*** BORG_EXIT_CODES=*** borg extract --remote-path borg --log-json --debug --list --show-rc --stdout /home/witten/Downloads/tmp/test.borg::flux-2026-07-20T18:59:25.829646 sh:borgmatic/bootstrap/manifest.json > -1
Bootstrapping configuration paths: /home/witten/Downloads/tmp/test.yaml
BORG_RELOCATED_REPO_ACCESS_IS_OK=*** BORG_EXIT_CODES=*** borg extract --remote-path borg --log-json --debug --list --show-rc /home/witten/Downloads/tmp/test.borg::flux-2026-07-20T18:59:25.829646 home/witten/Downloads/tmp/test.yaml
using builtin fallback logging configuration
33 self tests completed in 0.08 seconds
Verified integrity of /home/witten/Downloads/tmp/test.borg/index.21
TAM-verified manifest
security: read previous location '/home/witten/Downloads/tmp/test.borg'
security: read manifest timestamp '2026-07-21T01:59:50.647462'
security: determined newest manifest timestamp as 2026-07-21T01:59:50.647462
security: repository checks ok, allowing access
Archive authentication DISABLED.
TAM-verified archive
home/witten/Downloads/tmp/test.yaml
terminating with success status, rc 0

summary:
/home/witten/Downloads/tmp/test.yaml: Loading configuration file
Bootstrap successful

Other notes / implementation ideas

The above correct debug logs appear when you add --config test.yaml (with any valid config file) on the command-line. This is because there's now in-memory config file data to set the --verbosity value into, which is how borgmatic actually accesses the verbosity in order to configure logging at the relevant level.

borgmatic version

main

borgmatic installation method

uv tool install --editable

Borg version

1.4.4

Python version

3.14.16

Database version (if applicable)

No response

Operating system and version

Manjaro stable

### What I'm trying to do and why Due to its expected use case of being run on a fresh system before borgmatic is set up yet, the `bootstrap` action does not expect borgmatic configuration. However, due to a quirk in the way that command-line arguments override configuration file options, if you run `bootstrap` with a `--verbosity` flag, then `bootstrap` ignores that value *unless* you also provide a configuration file, e.g. with `--config`. ### Steps to reproduce ```bash $ borgmatic -v 2 config bootstrap --repository test.borg ``` ### Actual behavior ``` summary: Bootstrap successful ``` (Note the lack of debug logs.) ### Expected behavior ``` BORG_EXIT_CODES=*** borg --version --log-json --debug --show-rc BORG_RELOCATED_REPO_ACCESS_IS_OK=*** BORG_EXIT_CODES=*** borg info --remote-path borg --log-json --glob-archives {hostname}-* --json test.borg BORG_RELOCATED_REPO_ACCESS_IS_OK=*** BORG_EXIT_CODES=*** borg list --remote-path borg --log-json --glob-archives {hostname}-* --last 1 --json test.borg Latest archive is flux-2026-07-20T18:59:25.829646 (3ad16973e49b6c5614c000b4c642e4cc8e7c997e24897b124ea45f011874d0b7) Using runtime directory /run/user/1000/borgmatic BORG_RELOCATED_REPO_ACCESS_IS_OK=*** BORG_EXIT_CODES=*** borg extract --remote-path borg --log-json --debug --list --show-rc --stdout /home/witten/Downloads/tmp/test.borg::flux-2026-07-20T18:59:25.829646 sh:borgmatic/bootstrap/manifest.json > -1 Bootstrapping configuration paths: /home/witten/Downloads/tmp/test.yaml BORG_RELOCATED_REPO_ACCESS_IS_OK=*** BORG_EXIT_CODES=*** borg extract --remote-path borg --log-json --debug --list --show-rc /home/witten/Downloads/tmp/test.borg::flux-2026-07-20T18:59:25.829646 home/witten/Downloads/tmp/test.yaml using builtin fallback logging configuration 33 self tests completed in 0.08 seconds Verified integrity of /home/witten/Downloads/tmp/test.borg/index.21 TAM-verified manifest security: read previous location '/home/witten/Downloads/tmp/test.borg' security: read manifest timestamp '2026-07-21T01:59:50.647462' security: determined newest manifest timestamp as 2026-07-21T01:59:50.647462 security: repository checks ok, allowing access Archive authentication DISABLED. TAM-verified archive home/witten/Downloads/tmp/test.yaml terminating with success status, rc 0 summary: /home/witten/Downloads/tmp/test.yaml: Loading configuration file Bootstrap successful ``` ### Other notes / implementation ideas The above correct debug logs appear when you add `--config test.yaml` (with any valid config file) on the command-line. This is because there's now in-memory config file data to set the `--verbosity` value *into*, which is how borgmatic actually accesses the verbosity in order to configure logging at the relevant level. ### borgmatic version main ### borgmatic installation method uv tool install --editable ### Borg version 1.4.4 ### Python version 3.14.16 ### Database version (if applicable) _No response_ ### Operating system and version Manjaro stable

witten added the

bug

label 2026-07-23 17:18:30 +00:00

witten changed title from bootstrap action ignores "--verbosity" unless "--config" flag is also used to bootstrap action ignores "--verbosity" when no configuration is present 2026-08-02 00:04:14 +00:00

witten referenced this issue from a commit 2026-08-02 00:04:47 +00:00

Fix for the "bootstrap" action ignoring the "--verbosity" flag when no configuration is present (#1336).

witten commented 2026-08-02 00:05:39 +00:00

Author

Owner

Copy link

Fixed in main! Will be part of the next release.

Fixed in main! Will be part of the next release.

witten closed this issue 2026-08-02 00:05:39 +00:00

witten commented 2026-08-14 20:16:45 +00:00

Author

Owner

Copy link

Released in borgmatic 2.1.7!

Released in borgmatic 2.1.7!

Sign in to join this conversation.

No Branch/Tag specified

Branches Tags

main

parallel-borgmatic

command-hook-steps

2.1.7

2.1.6

2.1.5

2.1.4

2.1.3

2.1.2

2.1.1

2.1.0

2.0.13

2.0.12

2.0.11

2.0.10

2.0.9

2.0.8

2.0.7

2.0.6

2.0.5

2.0.4

2.0.3

2.0.2

2.0.1

2.0.0

1.9.14

1.9.13

1.9.12

1.9.11

1.9.10

1.9.9

1.9.8

1.9.7

1.9.6

1.9.5

1.9.4

1.9.3

1.9.2

1.9.1

1.9.0

1.8.14

1.8.13

1.8.12

1.8.11

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   

blocked

  

breaking

  

bug

  

data loss

  

design finalized

  

good first issue

  

new feature area

  

question / support

  

security

  

waiting for response

No labels

blocked

breaking

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

1 participant

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

No description provided.