Konstantin Lebedev

It seems that at the start of s3 it is not difficult to get a list of packages @chrislusf But it is not clear how best to update, it seems...

> How about `NoSuchBucket` or `InvalidRequest` No need to change handles from cors and policy as they are not implemented

> How about put this option into the filer.toml file? Similar to this? > > ``` > [filer.options] > # with http DELETE, by default the filer would check whether...

Maybe you should create a separate branch for this feature or pour it into the master with small changes

This is ok for Etag as you use different chunk size settings.

@chrislusf It seems that you need to synchronize the chunk size for each file everywhere https://github.com/chrislusf/seaweedfs/blob/04663c3611326a8bac87d47fc4a2c546c6d9acdd/weed/remote_storage/s3/s3_storage_client.go#L148

@remram44 In terms of the life of a master in k8s where any change results in a restart of the container, this is unnecessary.

> @kmlebedev Sorry, I don't understand you don't really need a reload master

Zero step https://github.com/seaweedfs/seaweedfs/pull/3755

Let's run the unit tests before the merge iam ? https://github.com/ceph/s3-tests ``` S3TEST_CONF=your.conf ./virtualenv/bin/nosetests s3tests_boto3.functional.test_iam ```