Implement automatic cleanup when pull-through caching fails or its main distribution is removed
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 31
- Forks
- 56
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 22
Description
At the moment, when the pulling fails in the middle of the execution, we may end up having some left-overs in the database. Similarly, when a user decides to remove a pull-through caching distribution, we should give her a way to remove everything, including created sub-distributions, remotes, and repositories.
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
Trace the pull-through caching failure path and distribution-removal path, then inspect how sub-distributions, remotes, repositories, and database records are persisted. Done means failed pulls leave no leftovers and removing a pull-through caching distribution can clean up all created resources; add or run relevant tests found beside those paths.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend, database
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100