Project

Profile

Help

Story #5254

mirror mode cannot be set on a remote

Added by jsherril@redhat.com 2 months ago. Updated 2 months ago.

Status:
NEW
Priority:
Normal
Assignee:
-
Category:
-
Sprint/Milestone:
-
Start date:
Due date:
% Done:

0%

Platform Release:
Blocks Release:
Backwards Incompatible:
No
Groomed:
No
Sprint Candidate:
No
Tags:
Katello-P3
QA Contact:
Complexity:
Smash Test:
Verified:
No
Verification Required:
No
Sprint:

Description

The various remotes do not support setting the 'mirror' mode, it was removed as part of: https://pulp.plan.io/issues/3492

I had expressed some concern here: https://www.redhat.com/archives/pulp-dev/2018-March/msg00058.html
but it seemed to not get any attention. In the meantime it sees that download policy was added back to the remotes.

History

#1 Updated by daviddavis 2 months ago

  • Tracker changed from Issue to Story
  • % Done set to 0

The reason we removed mirror from remotes is that different repos sharing a remote might want different behaviors (ie one repo does a mirror sync while the other uses additive). I've thought that perhaps we should join remotes to repos (many-to-many) like git does and perhaps this join model could store the mirror value.

There was a concern raised that perhaps some plugins wouldn't use mirror and that it should belong in the plugin and not core. However, I think the argument could be made for many of the fields on remote (eg policy, ssl config, etc).

#2 Updated by WilliamGoins 2 months ago

daviddavis wrote:

The reason we removed mirror from remotes is that different repos sharing a remote might want different behaviors (ie one repo does a mirror sync while the other uses additive). I've thought that perhaps we should join remotes to repos (many-to-many) like git does and perhaps this join model could store the mirror value. online essay typer

I see. Thanks for clarification.

Please register to edit this issue

Also available in: Atom PDF