Recording upload: option to replace an already imported format
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 6
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Sometimes a playback format needs to be uploaded again after it was already
imported: a format that is (re)generated by a post-processing step after the
initial publish, a broken playback that was fixed on the BBB server, or media
files that were re-encoded. Re-importing an existing format is silently skipped by design
Skipping file copy because target directory exists: .../storage/<tenant>/<record_id>/<format>
I would suggest to add an opt-in way to replace an existing format on upload, e.g. a query parameter:
POST /bbblb/api/v1/recording/upload?replace=true
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 at the recording upload API endpoint and trace the existing behavior that skips copying when the target format directory exists. Implement an opt-in replace=true request path while preserving the current default, then verify uploads for both existing and new formats behave as intended.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 58/100