Project

Profile

Help

Story #8049

closed

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

Added by fao89 over 1 year ago. Updated 11 months ago.

Status:
CLOSED - DUPLICATE
Priority:
Normal
Assignee:
-
Sprint/Milestone:
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

Related to Ansible Plugin - Issue #8047: New artifact is downloaded even when we already have a content unit with the same identityCLOSED - DUPLICATEActions
Actions #1

Updated by fao89 over 1 year ago

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

Updated by fao89 about 1 year ago

  • Sprint/Milestone set to 1.0.0 - Candidates
Actions #3

Updated by pulpbot 11 months ago

  • Description updated (diff)
  • Status changed from NEW to CLOSED - DUPLICATE

Also available in: Atom PDF