)]}'
{"/PATCHSET_LEVEL":[{"author":{"_account_id":1179,"name":"Clay Gerrard","email":"clay.gerrard@gmail.com","username":"clay-gerrard"},"change_message_id":"97ae52411b656bb5e600cd1b2cfef7f648cb0eb0","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"a96b0b45_95b89e54","updated":"2022-06-03 21:06:51.000000000","message":"I found some docs https://docs.aws.amazon.com/AmazonS3/latest/userguide/acl-overview.html#canned-acl\n\nand wrote some more tests https://review.opendev.org/c/openstack/swift/+/844643\n\nI had trouble parsing how bucket-owner-read and bucket-owner-full-control could have the same ACLs but I guess in both cases the object owner has full control - so the difference is really just about how the container/bucket owner can access the object.  But I don\u0027t think there\u0027s a way to put an object in a swift container w/o the owner being able to read/write that object, so really maybe these object ACLs just do not matter at all.\n\nI think this can merge w/o messing anyone up - and it\u0027ll work better with newer AWS Java client librarys that are always going to send this BucketOwnerFullControl canned ACL","commit_id":"c33b3d860fd81db8e835df69914fc36b902dcbda"}]}