You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With the introduction of Django 4.2, the storages.backends.s3boto3.S3Boto3Storage backend now accepts additional options for configuration. However, I noticed that there are currently no options to configure CloudFront settings directly through these storage options.
Currently it is possible to set AWS_CLOUDFRONT_KEY_ID and AWS_CLOUDFRONT_KEY which would have effect to all storages.
In my specific use case, I require the cloudfront_key_id and cloudfront_key to be set for the CloudFrontSigner. I used to configure this manually in the constructor of my custom S3Boto3Storage subclass, but I think it would be beneficial to have this as part of the official library.
I propose to extend the options for S3Boto3Storage to accept cloudfront_key_id and cloudfront_key. If these options are provided, S3Boto3Storage would create and store an instance of CloudFrontSigner with these credentials.
I would appreciate it if you could consider adding this feature to the library. It would allow a more flexible configuration of S3Boto3Storage and CloudFront in Django 4.2 and later versions. I am willing to contribute to this feature if needed.
The text was updated successfully, but these errors were encountered:
With the introduction of Django 4.2, the storages.backends.s3boto3.S3Boto3Storage backend now accepts additional options for configuration. However, I noticed that there are currently no options to configure CloudFront settings directly through these storage options.
Currently it is possible to set
AWS_CLOUDFRONT_KEY_ID
andAWS_CLOUDFRONT_KEY
which would have effect to all storages.In my specific use case, I require the cloudfront_key_id and cloudfront_key to be set for the CloudFrontSigner. I used to configure this manually in the constructor of my custom S3Boto3Storage subclass, but I think it would be beneficial to have this as part of the official library.
I propose to extend the options for S3Boto3Storage to accept cloudfront_key_id and cloudfront_key. If these options are provided, S3Boto3Storage would create and store an instance of CloudFrontSigner with these credentials.
Example:
I would appreciate it if you could consider adding this feature to the library. It would allow a more flexible configuration of S3Boto3Storage and CloudFront in Django 4.2 and later versions. I am willing to contribute to this feature if needed.
The text was updated successfully, but these errors were encountered: