This is awesome! Content length is no longer a separate required argument to `put` it seems then - w
This is awesome! Content length is no longer a separate required argument to
put it seems then - woot!putReadableStream must be known. For example, incoming request with a content-length and you're forwarding along the body. Or the response body of a fetch that has a content-length. Or the readable half of a FixedLengthStream transform stream.r2_public_beta_bindings is a compat flag right ok, makes senser2_public_beta_bindings is on by default but for those that need to upgrade the compat date but keep the old bindings, you can opt to the old bindings via r2_internal_beta_bindings. Anyone starting should use the public beta bindings. The old ones are not as complete and have edges.expirationTtl was never a thing and was never hooked up to anything IIRC (or maybe it was actually setting the cache expiry header? can't recall). There is a plan around it and we will reintroduce but we probably need to have object lifecycles comprehensively solved (although maybe we put in a hack before then - hard to say. we'll see how things develop). Talk to us internally if you absolutely need it but most likely our answer will be no.include field which is strange since it's R2 specific. This is what is should be instead:R2Object list will have a httpMetadata/customMetadata populated. The performance notes are very preliminary and I wouldn't take them too seriously. Design around what's easiest for now. The performance of the system will be changing drastically in the coming weeks.x-amz-meta-directive which lets you update key/values without having to know the entire set ahead of timecontent-lengthcontent-lengthFixedLengthStreamr2_public_beta_bindingsr2_public_beta_bindingsr2_internal_beta_bindingsexpirationTtlinclude/**
* If you populate this array, then items returned will include this metadata.
* A tradeoff is that fewer results may be returned depending on how big this
* data is. For now the caps are TBD but expect the total memory usage for a list
* operation may need to be <1MB or even <128kb depending on how many list operations
* you are sending into one bucket. Make sure to look at `truncated` for the result
* rather than having logic like
* */
include: ("httpMetadata" | "customMetadata")[]R2ObjecthttpMetadatacustomMetadatax-amz-meta-directive