Store mirror configurations on the remote data model
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 598
- Forks
- 168
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 86
Description
Author: @newswangerd (newswangerd)
Redmine Issue: 7808, https://pulp.plan.io/issues/7808
Right now whenever a sync is performed the client has to pass whether or not the remote should mirror the content as a parameter when the sync is performed. It would be useful to be able to save this in the database so this parameter could be configured server side if the user wants the a remote to behave the same across all repos that it syncs to.
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 tracing the remote data model and the sync operation described in the issue, focusing on how the mirror setting is currently passed by the client. Done means the mirror configuration can be stored server-side for a remote and consistently used across repositories it syncs to.
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
- 35/100