Project

Profile

Help

Send by e-mail

Issue #3880

manifest list os and arch attributes on manifests themselves

Added by tomckay@redhat.com over 1 year ago. Updated 9 months ago.

Status:
CLOSED - WONTFIX
Priority:
Normal
Assignee:
-
Category:
-
Sprint/Milestone:
-
Start date:
Due date:
Severity:
2. Medium
Version - Docker:
Platform Release:
Blocks Release:
Target Release - Docker:
OS:
Backwards Incompatible:
No
Triaged:
No
Groomed:
No
Sprint Candidate:
No
Tags:
Pulp 2
QA Contact:
Complexity:
Smash Test:
Verified:
No
Verification Required:
No
Sprint:

Description

Related to https://pulp.plan.io/issues/3137 I see that os/arch is present in the array of manifests associated with a manifest list. I am wondering if that information can/should be stored on the manifests themselves as well.

I understand that the docker schema does not do this but it seems like it would be useful information when browsing manifests. Or am I misunderstanding and a manifest may belong to more than one manifest list and be associated with more than one os/arch pairing.

History

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

exactly, we cannot store the information on the manifest taken from the manifest list, especially when manifests can be cross referenced in the manifest lists ---> may belong to more than one manifest list and be associated with more than one os/arch pairing.

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

  • Status changed from NEW to CLOSED - WONTFIX

#3 Updated by bmbouter 9 months ago

  • Tags Pulp 2 added

Please register to edit this issue

Send by e-mail

Also available in: Atom PDF