Story #3055
closed
As a user, I can publish a Yum repository that works with repo_gpgcheck=1
Status:
CLOSED - CURRENTRELEASE
Description
To allow a Yum repository to be used with Yum clients that have repo_gpgcheck=1 configured in /etc/yum.conf:
- Create a new GPG signing key that can be used by Pulp worker processes without a password. (Documentation provides example procedures.)
- Append the public key associated with the new GPG signing key to the gpgkey file specified in the distributor config for the Yum repository in Pulp.
- Set gpg_sign_metadata to True in the distributor config for the Yum repository in Pulp.
See also https://access.redhat.com/solutions/2850911
- Tracker changed from Issue to Story
- % Done set to 0
- Subject changed from Pulp does not generate repomd.xml.asc files needed by yum repo_gpgcheck to As a user, I can publish a Yum repository that works with repo_gpgcheck=1
- Description updated (diff)
- Status changed from NEW to POST
- Assignee set to PaulSD
So this feature defaults to off because it's only enabled if the user specifies gpg_sign_metadata=True right?
As an FYI, we do have an integration test suite called pulp-smash which is run by ichimonji10 in #pulp-dev in case you are interested in writing any tests to use and verify this feature. Whatever you want to do is fine of course. Thanks for contributing this great feature.
Correct, it defaults to off. I implemented it this way because this feature will not work unless the user first manually prepares and distributes a GPG signing key.
- Status changed from POST to MODIFIED
- % Done changed from 0 to 100
- Project changed from Pulp to RPM Support
- Platform Release set to 2.15.0
- Status changed from MODIFIED to 5
- Status changed from 5 to CLOSED - CURRENTRELEASE
Do we have a tracker for Pulp 3 functionality? Or can we comment if Pulp 3 rpm plugin has parity with this functionality?
Also available in: Atom
PDF
.
Add support for generation of repomd.xml.asc files
fixes #3055 https://pulp.plan.io/issues/3055