Actions
Issue #9546
closed
When syncing a collection version, all its signatures must be also included
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
Actions
.