github/restic
4
0 Fork 0
mirror of https://github.com/restic/restic.git synced 2026-11-13 14:42:03 +00:00
Code Issues Releases Wiki Activity

do not require gs bucket permissions to init repository

Browse Source 
a gs service account may only have object permissions on an existing
bucket but no bucket create/get permissions.

these service accounts currently are blocked from initialization a
restic repository because restic can not determine if the bucket exists.

this PR updates the logic to assume the bucket exists when the bucket
attribute request results in a permissions denied error.

this way, restic can still initialize a repository if the service
account does have object permissions

fixes: https://github.com/restic/restic/issues/3100
This commit is contained in:
eleith committed 2020-11-18 06:14:11 -08:00
1 parent 5f3b802ee7
commit a24e986b2b
2 files changed
+15
Download Patch File Download Diff File Expand all files Collapse all files

No files matched your search

changelog/unreleased/issue-3100
+10
View File
@@ -0,0 +1,10 @@
Bugfix: Do not require gs bucket permissions when running init
Restic used to require bucket level permissions for the gs backend
in order to initialize a restic repository.
It now allows a gs service account to initialize a repository if the
bucket does exist and the service account has permissions to write/read
to that bucket.
https://github.com/restic/restic/issues/3100