upstream/restic
1
0
Fork 0
mirror of https://github.com/restic/restic.git synced 2025-12-20 23:00:24 -05:00
Code Issues Projects Releases Packages Wiki Activity Actions
restic/changelog/0.12.0_2021-02-14/issue-3100

11 lines
386 B
Text
Raw Normal View History

changelog: Correct and slightly polish some unreleased changelog files
2021-02-13 18:57:54 -05:00
Bugfix: Do not require gs bucket permissions when running `init`
do not require gs bucket permissions to init repository 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
2020-11-17 19:44:26 -05:00
changelog: Correct and slightly polish some unreleased changelog files
2021-02-13 18:57:54 -05:00
Restic used to require bucket level permissions for the `gs` backend
do not require gs bucket permissions to init repository 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
2020-11-17 19:44:26 -05:00
in order to initialize a restic repository.
changelog: Correct and slightly polish some unreleased changelog files
2021-02-13 18:57:54 -05:00
It now allows a `gs` service account to initialize a repository if the
do not require gs bucket permissions to init repository 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
2020-11-17 19:44:26 -05:00
bucket does exist and the service account has permissions to write/read
to that bucket.
https://github.com/restic/restic/issues/3100
Reference in a new issue Copy permalink