Create separate auto-expiring buckets for direct uploads
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 88
- Forks
- 37
- PR merge metrics
- No merged PRs in 30d
Description
Right now we are storing "directly uploaded" files on the same bucket both for the finalized processed files we keep for VOD.
This creates a lot of cruft in the VOD buckets since we have a lot of temporary data in there, with every asset being now charged twice (one for the upload file, one for the final destination where it goes).
We should have a dedicated bucket for the uploads instead which we can have different retention policies and better organization of files.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the direct-upload storage configuration and the path that moves finalized files into VOD storage. Define how a dedicated upload bucket and its retention policy should coexist with the existing VOD bucket, then verify temporary upload data is stored separately and cleaned up according to that policy.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- backend, cloud
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100