Google Drive upload fails silently when configuration is wrong

[maxi07]

Describe the bug
If the option 'GOOGLE_DRIVE_IMPERSONATE_SUBJECT' is not set in the .env file, the upload will fail silently.

Version (please complete the following information):

• Image Version: 2.47.1
• Docker Version: 4.61
• Docker Compose Version: 5.0.2

Additional context

docker compose exec backup backup
time=2026-02-20T15:45:03.116Z level=INFO msg="Stopping 1 out of 7 running container(s) as they were labeled docker-volume-backup.stop-during-backup=true or docker-volume-backup.stop-during-backup-no-restart=true."
time=2026-02-20T15:45:03.811Z level=INFO msg="Created backup of `/backup` at `/tmp/backup-2026-02-20T15-45-03.tar.gz`."
time=2026-02-20T15:45:03.979Z level=INFO msg="Restarted 1 out of 1 stopped container(s)."
time=2026-02-20T15:45:03.981Z level=INFO msg="Starting upload for backup 'backup-2026-02-20T15-45-03.tar.gz'." storage=GoogleDrive
time=2026-02-20T15:45:04.010Z level=INFO msg="Stored copy of backup `/tmp/backup-2026-02-20T15-45-03.tar.gz` in `/archive`." storage=Local
time=2026-02-20T15:45:12.389Z level=INFO msg="None of 2 existing backups were pruned." storage=Local
time=2026-02-20T15:45:12.744Z level=INFO msg="None of 0 existing backups were pruned." storage=GoogleDrive
time=2026-02-20T15:45:12.753Z level=INFO msg="Removed tar file `/tmp/backup-2026-02-20T15-45-03.tar.gz`."

[m90]

This value being required is mentioned in the docs:

This is required because your service account needs to act on behalf of a user in your organization in order to upload files.

However it definitely should not fail silently. I don't really understand why the Google Drive SDK doesn't reject such a configuration, so I'll have to look into it.

[m90]

I fixed this in #733 - I would think the bug is minor enough to defer releasing it for now and wait for more features and/or fixes, but if this being unreleased is a blocker for you, please lmk and I can cut a release.

[m90]

This now fixed in v2.47.2