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 |
||
|---|---|---|
| .. | ||
| .gitignore | ||
| issue-1681 | ||
| issue-1800 | ||
| issue-2186 | ||
| issue-2528 | ||
| issue-2688 | ||
| issue-3083 | ||
| issue-3090 | ||
| issue-3100 | ||
| pull-2718 | ||
| pull-2941 | ||
| pull-3006 | ||
| pull-3014 | ||
| pull-3048 | ||
| pull-3099 | ||