Andrew Gaul
Andrew Gaul
Please test with the latest master.
S3Proxy now uses both the AWS SDK v1 and v2 for tests so there is no blocker to writing a provider using the latter.
@klaudworks tagging you here if you are interested. There are a couple ways to approach this but looking at the initial commit for Azure b33f3e2826211b282c1c163438b1be452693f24c and [its evolution](https://github.com/gaul/s3proxy/commits/master/src/main/java/org/gaul/s3proxy/azureblob) might be...
Does setting `S3PROXY_IGNORE_UNKNOWN_HEADERS=true` resolve your symptoms?
Could you test with the latest master? I merged a workaround for #830.
I requested a higher limit from GitHub so let's see what they say before changing anything.
OpenStack Swift does support S3 multipart: https://docs.openstack.org/swift/latest/s3_compat.html so I would first look to see if you have a misconfiguration or are running an older version.
Could you replicate this in the S3Proxy unit tests? `AwsSdkTest.testBlobRemove` appears to do the same thing as your example so I wonder if there is some difference in the S3...
References #263.
Not shading the Docker artifact is fine in theory but in practice additional build configuration is fragile. I can merge something like this but if it breaks the build some...