[EPIC] Audit sync deletion calls in all viewsets
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 598
- Forks
- 168
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 86
Description
Sometimes deleting an object cascades to deleting multiple thousands of objects. This can stall or even timeout the gunicorn worker. In such cases, pulp tasks should be used. However switching to asynchronous deletion is changing the api slightly.
What we identified so far is that Publications, Exports and Uploads may be problematic.
One Idea that would help and make the codebase cleaner is to turn Upload chunks into Artifacts.
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 auditing the viewsets for Publications, Exports, and Uploads, focusing on synchronous deletion calls and their cascading effects. Determine which deletions require pulp tasks and document the API changes needed for asynchronous behavior. Also investigate whether turning Upload chunks into Artifacts belongs in this work; completion requires a scoped plan for the affected areas.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api, backend
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100