Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

S3 Proxy GetBucketAcl incorrect result #336

Closed
jonaustin09 opened this issue Dec 12, 2023 · 1 comment
Closed

S3 Proxy GetBucketAcl incorrect result #336

jonaustin09 opened this issue Dec 12, 2023 · 1 comment
Labels
bug Something isn't working

Comments

@jonaustin09
Copy link
Contributor

Describe the bug
When running GetBucketAcl_success integration test, it returns incorrect result.

Result
expected grants to be [{0x1400031e040 FULL_CONTROL {}} {0x1400031e080 READ_ACP {}} {0x1400031e0c0 WRITE {}}], instead got [{0x14000393dc0 FULL_CONTROL {}} {0x140004100c0 READ_ACP {}} {0x140004103c0 WRITE {}}]

To Reproduce

./versitygw test -a a -s s --endpoint http://localhost:7071 GetBucketAcl_success

Expected behavior
It has to successfully pass the integration test

@jonaustin09 jonaustin09 added the bug Something isn't working label Dec 12, 2023
@benmcclelland
Copy link
Member

for this one, I think we need a way to store our own ACLs separately from the backend ACLs. So we dont want to forward the ACL to the backend, we need to encode it in the bucket metadata or something else.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants