s3proxy
s3proxy copied to clipboard
Restore OPAQUE_MARKERS handling for list objects V1
We need this to support V1 clients that use the last object name in the response as a marker for the next page (which is allowed according to the S3 docs).
@Decard6 This partially reverts changes in https://github.com/gaul/s3proxy/pull/531
I'm concerned that s3-tests isn't exercising this behavior. Can you look at these and see what's missing?
Do we have automated testing against a real azure blob store?
@gaul Could you give me some pointers to where this should be tested?
The ideal way to test this is https://github.com/ceph/s3-tests which I periodically rebase onto. But I don't have any automated integration tests against Azure presently.
Alternatively maybe we could parameterize some S3Proxy listObjects tests to toggle OPAQUE_MARKERS
? I'm happy to merge this PR but just want to make sure that we have some way to avoid future regressions.
@larshagencognite could you rebase this change?
@Decard6 any thoughts here?