Description
We've deployed S3Proxy to an AKS cluster to be the proxy in front of Azure Storage. Half the blobs we upload are below the default 4MB limit for multi-part uploads to Azure, the other blobs start at 25MB.
These 25MB files are causing us some problems, namely when we push these through the proxy they increase in size. It appears the data is appended to the already stored blob instead of the blob being replaced.
We are currently working around this problem by first sending a delete command, but would prefer that the functionality works as expected.
When we test the same application code again Min.IO we do not observe this growing file size problem, nor when we directly use the Azure API.
Perhaps we missed some configuration option? If not, have we discovered a bug?