Closed mgzwarrior closed 3 months ago
Thanks for the report.
The deprecated name is just an alias for the base one.
Am a bit confused about how this is possible because the BaseSettings
should populate the client_config
property. This seems like a thing where the test suite should fail.
Do you have any insight into how you ended up with this error?
Thanks for the report.
The deprecated name is just an alias for the base one.
Am a bit confused about how this is possible because the
BaseSettings
should populate theclient_config
property. This seems like a thing where the test suite should fail.Do you have any insight into how you ended up with this error?
I don't have any deeper insights because we "solved" this by pinning to version 1.14.2
for now. If I have some free time this week, I will dig a bit deeper and see if I can figure anything out. I would like to clean up the use of S3Boto3Storage
in favor of the regular S3Storage
since it sounds like they are identical in functionality.
I agree that it feels like a test should fail if this was truly an issue.
Not an issue please see my comment: https://github.com/jschneier/django-storages/pull/1386#discussion_r1643372905
https://github.com/jschneier/django-storages/pull/1386
Here is the error that we received:
See here - https://github.com/jschneier/django-storages/pull/1386/files#r1640348739
Note that we are currently using
S3Boto3Storage
which is deprecated. We have a custom storage like this that provides default settings, plus a number of custom settings via env variables: