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

pulpbot · 2021-11-17T19:42:20Z

Author: @rochacbruno (rochacbruno)

Redmine Issue: 9546, https://pulp.plan.io/issues/9546

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

Add new signature model CollectionVersionSignature Add new content API to view CollectionVersionSignatures Add new sign task to repository endpoint to create new CollectionVersionSignatures Add new signature metadata to CollectionVersion Galaxy V3 API to enable syncing of signatures fixes: pulp#748 fixes: pulp#757 fixes: pulp#758

Add new signature model CollectionVersionSignature Add new content API to view CollectionVersionSignatures Add new sign task to repository endpoint to create new CollectionVersionSignatures Add new signature metadata to CollectionVersion Galaxy V3 API to enable syncing of signatures fixes: #748 fixes: #757 fixes: #758

pulpbot added Issue Migrated from Redmine New Severity: Medium labels Nov 17, 2021

gerrod3 linked a pull request Jan 19, 2022 that will close this issue

CollectionVersion Signature Support #754

Merged

3 tasks

gerrod3 closed this as completed in #754 Jan 24, 2022

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

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

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

pulpbot commented Nov 17, 2021

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

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

Comments

pulpbot commented Nov 17, 2021