Project

Profile

Help

Story #7356

As a user I can name a repo version and rollback to a named repo version

Added by ipanova@redhat.com over 1 year ago. Updated about 1 year ago.

Status:
CLOSED - WONTFIX
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

If a repo version would have a name, it would be easy to identify to which version to rollback.

Imagine you have 50 repo versions, and repo version 30 has name 'stable'. This way it would be easier to roll back to repo version 'stable' then keeping in mind numbers and knowing what corresponds to what.

By default name would be empty unless explicitly set. For any call to our REST api we could additionally provide a name. RepoVersion will stay immutable.

Another option would be to set the name for the repo version after its creation but that would not keep the RV immutable.

History

#1 Updated by ipanova@redhat.com over 1 year ago

  • Subject changed from As a user I can name a repo version to As a user I can name a repo version and rollback to a named repo version

#2 Updated by ipanova@redhat.com over 1 year ago

  • Description updated (diff)

#3 Updated by ipanova@redhat.com over 1 year ago

  • Description updated (diff)

#4 Updated by ipanova@redhat.com over 1 year ago

  • Description updated (diff)

#5 Updated by ipanova@redhat.com over 1 year ago

  • Tracker changed from Story to Issue
  • Severity set to 2. Medium
  • Triaged set to No

#6 Updated by ttereshc over 1 year ago

How is it different from a label story/idea? (I'll try find an issue)

#7 Updated by fao89 over 1 year ago

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

#8 Updated by ipanova@redhat.com over 1 year ago

ttereshc wrote:

How is it different from a label story/idea? (I'll try find an issue)

https://pulp.plan.io/issues/7127 here is the issue. The way it is drafted now the labels will be used for querying and filtering as a key-value store

#9 Updated by ipanova@redhat.com over 1 year ago

As per open floor discussion:

  • we have eliminated the idea of naming a RV, because the name is supposed to be re-used. This conflicts with the RV staying immutable.
  • we have discussed usage of labels, since labels are a key-value store we could use boolean stable=1.Doable but strange. Another possible form of usage could be name=stable. Labels do not offer constrains meaning within a repo you could have X repoversions labeled stable
  • the other idea would be to have a string/tag; it would imply some uniqueness in place - so there can be only one RV within a repo that is marked as 'stable'

We need to work more on the user stories to understand what would be the best fit.

#10 Updated by dkliban@redhat.com about 1 year ago

  • Status changed from NEW to CLOSED - WONTFIX

Let's open a new issue for being able to create a label for a repository version.

Also available in: Atom PDF