[Pulp-dev] Should signing service be associated with Publication or Repository?

Dennis Kliban dkliban at redhat.com
Fri Mar 20 03:13:23 UTC 2020

RPM plugin allows users to define a signing service per repository. All
publications created from repository versions of that repository are signed
with that signing service.

The Debian plugin requires the user to specify the signing service each
time a publication is created. The signing service foreign key is stored
with each publication.

Even though the implementation in Debian requires the user to provide the
service href each time a publication is created, it seems like a stronger
model. The signing service associated with a repository can change thus
making it challenging to keep track of which signing service was used to
create a publication.

We should change the behavior in the RPM plugin before we release this
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/pulp-dev/attachments/20200319/91654a17/attachment.htm>

More information about the Pulp-dev mailing list