Nick Craig-Wood f56ea2bee2 s3: fix no error being returned when creating a bucket we don't own ... Before this change if you tried to create a bucket that already existed, but someone else owned then rclone did not return an error. This now will return an error on providers that return the AlreadyOwnedByYou error code or no error on bucket creation of an existing bucket owned by you. This introduces a new provider quirk and this has been set or cleared for as many providers as can be tested. This can be overridden by the --s3-use-already-exists flag. Fixes #7351		2023-10-09 18:15:02 +01:00
..
gen_setfrom.go	s3: refactor to use generated code instead of reflection to copy structs	2022-08-05 16:45:23 +01:00
s3_internal_test.go	s3: fix no error being returned when creating a bucket we don't own	2023-10-09 18:15:02 +01:00
s3_test.go	s3: empty directory markers - #3453	2023-04-28 14:31:05 +01:00
s3.go	s3: fix no error being returned when creating a bucket we don't own	2023-10-09 18:15:02 +01:00
setfrom.go	s3: refactor to use generated code instead of reflection to copy structs	2022-08-05 16:45:23 +01:00
v2sign.go	s3: v3sign: add missing subresource delete	2023-05-14 11:25:52 +01:00