Actions
Story #8049
closedAs a user, I want to able to distinguish signed and unsigned Collections
Start date:
Due date:
% Done:
0%
Estimated time:
Platform Release:
Groomed:
No
Sprint Candidate:
No
Tags:
Sprint:
Quarter:
Description
Ticket moved to GitHub: "pulp/pulp_ansible/718":https://github.com/pulp/pulp_ansible/issues/718
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
Updated by fao89 almost 4 years ago
- Related to Issue #8047: New artifact is downloaded even when we already have a content unit with the same identity added
Updated by pulpbot about 3 years ago
- Description updated (diff)
- Status changed from NEW to CLOSED - DUPLICATE
Actions