Closed hkdahal closed 6 months ago
Can we get this merged into main?
Awaiting approval from @janko. Can you please review/approve accordingly for this change? thanks
@pokonski - can I get your feedback/approval on this Pull Request please? thanks
@hkdahal sorry I can't give you an approval, I'm not a maintainer of Shrine, just commented a potential improvement :) I too am waiting for this fix 🤞
pinging @janko for approval on this PR
+1
Thanks for the PR, looks good to me 👍🏻
Currently S3-compatible Cloudflare R2 does not support tagging_directive (https://developers.cloudflare.com/r2/api/s3/api/). This means, we cannot use shrine with tagging_directive. Thus, this Pull Request aims to expose copy_options.
By default, copy_options will have existing value:
{ tagging_directive: "REPLACE" }
For users like me, we can instantiate S3 store like below until Cloudflare is fully compatible (or just pass additional copy options):
Shrine::Storage::S3.new(bucket: BUCKET, copy_options: {}, **s3_options),
This will also solve: https://github.com/shrinerb/shrine/issues/662