Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clean up deprecated behaviors from the S3BotoStorage #636

Merged
merged 1 commit into from
Jun 7, 2020
Merged

Clean up deprecated behaviors from the S3BotoStorage #636

merged 1 commit into from
Jun 7, 2020

Commits on Jun 6, 2020

  1. Clean up deprecated behaviors from the S3BotoStorage

    The ACL deprecation warnings produced by S3BotoStorage can be a false
    positives and create _a lot_ of noise. I suggest the project move
    forward with removing these features as scheduled. Dropping the
    deprecated behavior now means:
    
    The minimum supported version of boto3 is now 1.4.4.
    
    The S3Boto3Storage backend no longer accepts the argument acl. Use the
    ACL key in AWS_S3_OBJECT_PARAMETERS instead.
    
    The S3Boto3Storage backend no longer accepts the argument bucket. Use
    bucket_name or the setting AWS_STORAGE_BUCKET_NAME instead.
    
    The S3Boto3Storage backend no longer automatically creates the bucket.
    Doing so had encouraged using overly broad credentials. As a result, the
    AWS_BUCKET_ACL setting has been removed.
    
    The S3Boto3Storage backend no longer not longer supports the settings
    AWS_DEFAULT_ACL, AWS_REDUCED_REDUNDANCY and AWS_S3_ENCRYPTION. They have
    been removed in favor of the AWS_S3_OBJECT_PARAMETERS setting. Using
    AWS_S3_OBJECT_PARAMETERS allows for full control over these S3
    parameters.
    
    The S3Boto3Storage backend no longer supports the undocumented
    AWS_PRELOAD_METADATA setting.
    jdufresne committed Jun 6, 2020
    Configuration menu
    Copy the full SHA
    b1e254b View commit details
    Browse the repository at this point in the history