new feature: Add support for `PutObjectAcl` on objects.

[PeterlitsZo]

Feature Description

I want to change existing object's ACL.

(And override the default ACL if we can).

Problem and Solution

#5358 says we need a way to set the ACL for objects and commit 740795c do add the default ACL... This commit make we can write objects with the default ACL but we cannot:

• Change existing object's ACL.
• Or override the default ACL (e.g. the default ACL is public-read but for object foobar.secret, I want to make it private-read).

Additional Context

No response

Are you willing to contribute to the development of this feature?

• Yes, I am willing to contribute to the development of this feature.

[Xuanwo]

I don’t know how to model this. Any ideas? I feel it might be part of the control plane of the data, which is hard for OpenDAL to unify.

Hi @PeterlitsZo, would you like to share more about your use cases? How often will you need to do such operations?

[PeterlitsZo]

I want to use OpenDAL instead of aws_sdk_s3 to operate S3. I have a bucket where I mix objects with different access permissions, for example, default private-read objects and public-read objects specifically for external access (I know about presigned URLs, but I do need public-read objects to preserve resources that can be accessed over the long term).

would you like to share more about your use cases? How often will you need to do such operations?

Currently, I use a Rust tool I wrote in a CI pipeline. One of its purposes is to sync artifacts to object storage and mark them as public-read, so that internal users can download them via GET requests. This operation is not very frequent—maybe only once or twice a week.

[PeterlitsZo]

I don’t know how to model this.

Yes unify those are hard... A dirty way is just modify Service trait to make it support modify_acl method, but it is kind of dirty.

[erickguan]

S3 could implement ACL as an object right? e.g.

• read(/file/_acl)
• read(/file).attached(/acl)