forked from TrueCloudLab/restic
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 |
||
---|---|---|
.. | ||
0.6.0_2017-05-29 | ||
0.6.1_2017-06-01 | ||
0.7.0_2017-07-01 | ||
0.7.1_2017-07-22 | ||
0.7.2_2017-09-13 | ||
0.7.3_2017-09-20 | ||
0.8.0_2017-11-26 | ||
0.8.1_2017-12-27 | ||
0.8.2_2018-02-17 | ||
0.8.3_2018-02-26 | ||
0.9.0_2018-05-21 | ||
0.9.1_2018-06-10 | ||
0.9.2_2018-08-06 | ||
0.9.3_2018-10-13 | ||
0.9.4_2019-01-06 | ||
0.9.5_2019-04-23 | ||
0.9.6_2019-11-22 | ||
0.10.0_2020-09-19 | ||
0.11.0_2020-11-05 | ||
unreleased | ||
changelog-github.tmpl | ||
CHANGELOG.tmpl | ||
TEMPLATE |