mirror of
https://github.com/octoleo/restic.git
synced 2024-12-27 04:32:40 +00:00
a24e986b2b
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
11 lines
382 B
Plaintext
11 lines
382 B
Plaintext
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
|