Project

Profile

Help

Story #8049

As a user, I want to able to distinguish signed and unsigned Collections

Added by fao89 10 months ago. Updated about 1 month ago.

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

0%

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

Description

Currently, as CollectionVersions are distinguished by name, namespace, and version. This makes pulp keeping the artifact from the first provenance and ignoring artifacts from other provenances. Ref: #8047

pulp_ansible should allow and differentiate signed from unsigned Collections. One possibility would be adding the provenance to the content's identity.

Note: At pulp_rpm, signed and unsigned content cannot be part of the same repo version https://github.com/pulp/pulp_rpm/blob/master/pulp_rpm/app/models/package.py#L233


Related issues

Related to Ansible Plugin - Issue #8047: New artifact is downloaded even when we already have a content unit with the same identityNEW<a title="Actions" class="icon-only icon-actions js-contextmenu" href="#">Actions</a>

History

#1 Updated by fao89 10 months ago

  • Related to Issue #8047: New artifact is downloaded even when we already have a content unit with the same identity added

#2 Updated by fao89 about 1 month ago

  • Sprint/Milestone set to 1.0.0 - Candidates

Please register to edit this issue

Also available in: Atom PDF