Project

Profile

Help

Issue #9546

When syncing a collection version, all its signatures must be also included

Added by rochacbruno about 1 month ago. Updated 10 days ago.

Status:
CLOSED - DUPLICATE
Priority:
Normal
Assignee:
-
Sprint/Milestone:
-
Start date:
Due date:
Estimated time:
Severity:
2. Medium
Platform Release:
OS:
Triaged:
No
Groomed:
No
Sprint Candidate:
No
Tags:
Sprint:
Quarter:

Description

Ticket moved to GitHub: "pulp/pulp_ansible/748":https://github.com/pulp/pulp_ansible/issues/748


Related to https://pulp.plan.io/issues/9543

Story:

  • All collections are signed on the host system
  • When syncing to another instance, together with all the artifacts/versions, signatures will also need to be synced
  • If for example a signature is corrupted on the source system, user may redo the signature, invalidate the current, do signature rotation and then the clients will need to re-sync to fetch new valid signatures

Related issues

Related to Pulp - Issue #9543: Define and Create a Model to store Content SignaturesCLOSED - DUPLICATE<a title="Actions" class="icon-only icon-actions js-contextmenu" href="#">Actions</a>

History

#1 Updated by rochacbruno about 1 month ago

  • Related to Issue #9543: Define and Create a Model to store Content Signatures added

#2 Updated by pulpbot 10 days ago

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

Also available in: Atom PDF