Joao Eduardo Luis

I think this issue can be moved to #388, because it's not necessarily related with the actual implementation of API endpoints (as tracked by #593 and where this issue is...

I think this deserves to be in a `s3gw-ui`-specific testing epic, alongside with the E2E testing and friends. I don't think this should be part of the UI Backend Epic...

@l-mb I believe it will depend on whether clients rely on checksums, but so far it doesn't seem like we're hitting issues with the s3tests on this one (it might...

@votdev assigning you as the owner of the effort. We'll figure it out as we go who should own individual items.

I think this needs to be addressed after v0.23.0. I suspect this will require a non-trivial effort. I believe we will have to document missing this transition in the support...

I believe the s3gw-ui backend has a decent amount of unit tests, albeit I'll concede they may not be testing _weird_ stuff. That said, pushing it until after v0.23.0.

No longer verified as of v0.21.0

Correcting myself: this no longer shows in the UI as a duplicate, but the admin ops API still returns a duplicate entry for the same bucket. Reopening. ```json [ {...

@0xavi0 is this by chance related with the discussion had for #838 ?

there's an on-going submission that aims at fixing the `docker-compose.yaml` file: https://github.com/aquarist-labs/s3gw/pull/816