eleith a24e986b2b 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-18 06:14:11 -08:00
..
config_test.go	Add Google Cloud Storage as backend	2017-08-06 21:47:55 +02:00
config.go	simplified prefix removal, removed unnecessary if-else statements	2019-06-30 23:34:47 +03:00
gs_test.go	gs: support authentication with access token	2020-07-22 16:23:03 +02:00
gs.go	do not require gs bucket permissions to init repository	2020-11-18 06:14:11 -08:00