publicRead ACL

[mj8894]

• handling defaultACL when creating a bucket file using write operation.

[sww314]

Storages should not do this. It will mangle any custom ACLs users put on their files outside of the django-storages.
The ACL is set only on create on purpose - it is a default.
Consider, this example:

1. Set default acl to projectPrivate.
2. Share with userA + userB outside of storages.
3. Save file with minor update.
4. userA + userB would not longer have access because of minor content change.

[mj8894]

I agree.

However, the idea here was to apply default acl to newly created files using write instead of save option.

[mj8894]

Made Changes to apply default acl only if a new blob is being uploaded to bucket, not affecting ACLs of the already available objects.

[cupojoe]

@sww314 Why hasn't this being merged? Anything we can do to get it in? In order for the library to respect the default ACL I had to do a pretty ugly workaround to use save instead of the recommended write.

[jschneier]

Fixed by #756.