Zarrbargo design document

[yarikoptic]

As it has been on our on our list of targets and we agreed that it is orthogonal (at least largely), it would be great to hear your current ideas on how it could/should be implemented. I think a design document PR would be great to see what you are thinking about.

[aaronkanzer]

@jjnesbitt @waxlamp

Here is a rough draft Design Doc that @kabilar and I used for our initial first pass at using AWS Cloudfront presigned cookies as a method of fast access to zarr assets in S3

• https://github.com/lincbrain/linc-archive/pull/111/files

Here is also our main PR that included the API endpoint that issued the cookies to the user
• https://github.com/lincbrain/linc-archive/pull/126/files

Let me know if you'd like to take a first pass at the design doc, meet prior, or have me take a peek -- happy to work with whatever your preference might be.

Cc @yarikoptic @satra

[yarikoptic]

just a note: I think such a document among tech details should describe the need , or provision refactoring to remove the need for EmbargoedZarrArchive which survived the

• 9fc81a4 : "Rip out embargoed models"

I feel that like for AssetBlob it should be sufficient to just define embargoed bool attribute as long as we keep embargoed zarrs in the same bucket/location as public zarrs.

[jjnesbitt]

Superseded by #2069.

"Zarrbargo" is really just the extension of the embargo re-design to include zarrs, which doesn't really entail a large overarching change. That PR description contains all the information that would be present in a design doc.