Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.Problem/Motivation
We want to use non forked amazon sdk - because we're storing our entities in DynamoDB.
But can't combine this with the Drupal amazons3 module because it adds caching capabilities to the stream wrapper.
These look worthy of upstream submission.
Proposed resolution
Submit caching changes upstream.
Unfork repo in composer.json
Remaining tasks
All
User interface changes
None
API changes
None
Comments
Comment #1
larowlanHappy to help out as needed
Comment #2
larowlanLooks like it is included upstream already?
https://github.com/aws/aws-sdk-php/commit/6d23e25dbaef8120fc4db253ed6df3...
Just waiting for a new release?
Comment #3
larowlanNew release was out today, that commit doesn't appear to be in it?
Comment #4
deviantintegral CreditAttribution: deviantintegral at Lullabot for NBCUniversal commentedThe PR for this was over at https://github.com/aws/aws-sdk-php/pull/536
The AWS team decided that this should be treated as a new feature and is going in the upcoming V3 SDK release. There was a similar decision for one of the hooks we add in.
You should be able to still use all of the DynamoDB classes? As long as you aren't requiring a specific version in another module, the patched SDK should be used transparently. If you have your own patches against DynamoDB classes, your best bet would be to fork the SDK and combine both patchsets into a '-p' release.
Comment #5
deviantintegral CreditAttribution: deviantintegral at Lullabot for NBCUniversal commented