Project

Profile

Help

Maintenance. Planio will be undergoing a scheduled maintenance this weekend. Between Saturday, July 24 at 9:00 UTC and Sunday, July 25, 22:00 UTC your account might observe occasional downtimes which may last up to several minutes in some cases.

Story #7808

Store mirror configurations on the remote data model

Added by newswangerd 9 months ago. Updated 9 months ago.

Status:
NEW
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

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.

History

#1 Updated by daviddavis 9 months 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.

#2 Updated by fao89 9 months ago

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

Please register to edit this issue

Also available in: Atom PDF