Allow setting a priority for remotes
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
Research direction
Start by tracing how remotes are created or modified and how package requests search available remotes. Define and implement priority ordering so lookup stops at the highest-priority remote containing the package, then verify the behavior with coverage for remote configuration and package retrieval.
Written by the indexing model from the issue text.
Description
Is your feature request related to a problem? Please describe.
I have the following scenario:
The Pulp instance should be configured to cache both Registry 1 and Registry 2.
The Pulp instance should prioritize the direct pull from Registry 1 rather than the pull through Registry 2, because Registry 2 is on cloud and there are associated costs to traffic.
The architecture of the scenario cannot be modified, hence the need of setting the priority among remotes.
Describe the solution you'd like
When creating/modifying a remote, there should be an option to set the priority of the remote.
When asking the Pulp instance for a package that is not in a repository, it should search the package through the available remotes by ordering them by priority, stopping at the first repository with the package that has the highest priority.
Describe alternatives you've considered
Modifying the scenario is not allowed, so there are no alternatives.
- Dominant language
- Python
- Stars
- 5
- Forks
- 24
- Avg merge
- 1d 6h
- Merged PRs (30d)
- 39
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.
More from pulp/pulp_maven
-
Difficulty 4/5 3-5 days Newbie friendliness 55/100
pulp/pulp_maven#392 ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
pulp/pulp_maven#377 ·
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
pulp/pulp_maven#345 ·
-
Feature Triage-Needed
Difficulty 5/5 Over a week Newbie friendliness 30/100
pulp/pulp_maven#309 ·
-
Feature Triage-Needed
Difficulty 5/5 Over a week Newbie friendliness 30/100
pulp/pulp_maven#293 ·
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
bancolombia/sentinel#23 ·
-
test md OpenCI
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
langchain-ai/deepagents#6450 ·
-
bug client
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100