-
Notifications
You must be signed in to change notification settings - Fork 124
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow to set gpgKey value for repository #2903
Comments
I'd prefer to see native support for obs-signd, as it would make Pulp more generally useful for other users/deployments. |
Can obs-signd be triggered by a signing service script as documented here? If not, how different is a call to signd? https://docs.pulpproject.org/pulpcore/workflows/signed-metadata.html |
@Conan-Kudo I agree about obs-signd, would you like to file a separate issue? Or @praiskup @mdellweg The mode of operation is a bit different and as far as I can tell (the documentation is... sparse) the primary value add is remote signing of RPM packages, though I suppose you can sign other things with it as well. Maybe someone with more background can add to this. |
You can sign RPM packages, RPM repos, Debian repos, container images, WSL images, ISOs, etc. using signd. It's a pretty flexible and generic signing system. |
Ok, it is filled here. Though it is |
I, as an admin, want to be able to set gpgKey value for a yum repository.
This is currently possible in the Pulp only if you enable
signing_service
. In Copr we useobs-signd
for signing packages.We want to be able to set
gpgKey
to the value o our choice.Alternatively, native support for obs-signd is a solution as well.
The text was updated successfully, but these errors were encountered: