Extend optimize feature to mirror=True sync policy

Open
#631 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
30/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
python
Domain
backend

Research direction

Start by reading the linked pull request 630 and the existing pulpcore mirror option. Investigate how sync policies and repository versions currently handle optimize mode, then determine the entry points needed for a dedicated AptMirror stage. Done means mirroring selected distributions or components without deleting content retained by optimize mode.

Written by the indexing model from the issue text.

Description

.feature

optimize mode currently does not work in combination with mirror=True sync policy, so we do not use them together: https://github.com/pulp/pulp_deb/pull/630

The reason is that since optimize mode does not add anything, mirror mode then goes ahead and deletes everything from the repo "since it is no longer in the upstream repo".

Our first attempt at using optimize in combination with mirror ended up in a dead end.

The new plan is to replace the pulpcore mirror option with a dedicated AptMirror stage, that is capable of mirroring individual distributions or components instead of just the entire new repository version.

Dominant language
Python
Stars
71
Forks
91
Avg merge
1d 19h
Merged PRs (30d)
22

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from pulp/pulp_deb

All issues in pulp/pulp_deb

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.