As a plugin-author, I can have an influence on the repository-repair process
Open
Nobody has claimed this yet.
Feature
- Dominant language
- Python
- Stars
- 598
- Forks
- 168
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 86
Description
Author: @ggainey (ggainey)
Redmine Issue: 9128, https://pulp.plan.io/issues/9128
pulp_rpm has run into problems that require repairing broken rpm-specific data. It would be nice if there were some way that a plugin could register an interest when /pulp/pulp/api/v3/repair/ is invoked, and do plugin-specific investigation/changes.
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 repository-repair API endpoint, /pulp/pulp/api/v3/repair/, and trace how repair requests are handled. Determine how plugins could register interest for plugin-specific investigation or changes, then verify that the repair process invokes that extension point for pulp_rpm data.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100