Fix --version from failing without config #890

New Issue

MrUnknownDE · 2026-04-06T00:28:04+02:00

MrUnknownDE commented

2026-04-06 00:28:04 +02:00

Originally created by @BlackDex on 10/6/2024

Since we added the option to show the web-vault version also when running --version this causes the config to always be validated. While this is not very bad in general, it could cause the command to quit during the config validation, and not show the version, but also errors. This is probably not very useful for this specific command, unlike the --backup for example.

To fix this, and preventing the config from being validated, i added an AtomicBool to check if we need to validate the config on first load. This prevents errors, and will just show the Vaultwarden version, and if possible the web-vault version too.

Fixes #5046

*Originally created by @BlackDex on 10/6/2024* Since we added the option to show the web-vault version also when running `--version` this causes the config to always be validated. While this is not very bad in general, it could cause the command to quit during the config validation, and not show the version, but also errors. This is probably not very useful for this specific command, unlike the `--backup` for example. To fix this, and preventing the config from being validated, i added an AtomicBool to check if we need to validate the config on first load. This prevents errors, and will just show the Vaultwarden version, and if possible the web-vault version too. Fixes #5046

MrUnknownDE closed this issue

2026-04-06 00:28:04 +02:00

Sign in to join this conversation.

No Label

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github/vaultwarden#890

Fix --version from failing without config #890

Fix `--version` from failing without config #890