Project

Profile

Help

Story #7808

closed

Store mirror configurations on the remote data model

Added by newswangerd over 3 years ago. Updated about 2 years ago.

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

0%

Estimated time:
Platform Release:
Groomed:
No
Sprint Candidate:
No
Tags:
Sprint:
Quarter:

Description

Ticket moved to GitHub: "pulp/pulpcore/1942":https://github.com/pulp/pulpcore/issues/1942


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.

Actions #1

Updated by daviddavis over 3 years ago

I definitely agree that storing this info would be valuable for users. Per semver, we have to keep the mirror param on the sync endpoint. The question is then how does the mirror param on sync work with remote.mirror?

A couple potential solutions:

  1. The mirror param on sync always overrides whatever remote mirror is. So essentially remote.mirror becomes a default value.
  2. The remote.mirror field accepts true/false/null. The mirror param on sync only can be supplied if remote.mirror == null, otherwise an error gets raised.
Actions #2

Updated by fao89 over 3 years ago

  • Tracker changed from Issue to Story
  • % Done set to 0
  • Severity deleted (2. Medium)
  • Triaged deleted (No)
Actions #3

Updated by pulpbot about 2 years ago

  • Description updated (diff)
  • Status changed from NEW to CLOSED - DUPLICATE

Also available in: Atom PDF