Add pull-through support to pulp_file
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 598
- Forks
- 168
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 86
Description
Is your feature request related to a problem? Please describe.
Pull-through code can't be tested end-to-end in pulpcore's CI because pulp_file doesn't support it.
While we do have unit tests for it, some regressions might not be caught on a production-like runner.
A recent example is https://github.com/pulp/pulpcore/issues/6429
Describe the solution you'd like
Implement pull-through caching in pulp_file.
Describe alternatives you've considered
We could not do it.
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 reading pulp_file's existing pull-through unit tests and the related pulpcore issue 6429 to understand the expected behavior. Trace how pulp_file integrates with pulpcore's production-like CI, and consider the work complete when pull-through caching is supported and exercised end-to-end there.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 40/100