Replace minio with boto3

[ivanistheone]

Summary

The current version of minio==3.0.3 is outdated and would be good to upgrade to newest version as part of the py3 rollout.

Context

While studio's vue-refactor branch under py3.7, I ran into some issues with minio.
see minio/minio-py#835
fixed in https://github.com/minio/minio-py/tree/5.0.6

So if we want to support py3.7 in the future we'll need to:

-minio==3.0.3
+minio==5.0.8   # = latest  (or at least 5.0.6)

There have been several changes to minio API between 3.0.3 (ours) and 5.x (latest):

• 5.0.0 Sep 11, 2019 Breaking change in select object API. See (Adding tags to content node causes slow performance #793) for more details.
• 4.0.0 Breaking API change get_bucket_policy and set_bucket_policy APIs now take the entire policy, canned policies are deprecated.

Looking at the changelog I saw several bugfix releases that seemed useful to have and could potentially avoid bugs in production.

Edit (Aron): since we only use the minio library to create the bucket, we should just replace this with boto3, which is already included by django-s3-storage.

Category

Select one: ENHANCEMENT

[aronasorman]

Minio here isn't too important. We only use it to create the bucket. After that, we use its S3-compatible API and use django_s3_storage to interact with Minio.

We can take a look at upgrading django_s3_storage instead, as that may have some important bugfixes.

I'll close this for now and then make a new issue.

[aronasorman]

Upon more thought, I think we should just remove minio and replace with boto3.