Story #6926
closed
As a user I can set/update repo_gpgcheck and gpg_check options
Status:
CLOSED - CURRENTRELEASE
Description
The generated config.repo defaults to gpgcheck=0 and there's currently no way (that I could find) to override that on the server-side.
Our current workflow injests the config.repo as-is from pulp, this would introduce an extra step along the way to update the gpg repo configuration (via file or command line).
Add repo_gpgcheck and gpg_check options to the publication so a value can be explicitly set.
Default value will be 0 ( disabled).
Right now we set repo_gpgcheck value based on the presence of the signing_servide - remove that logic.
As an outcome, gpg checks will be fully under user's control, user will enable/disable when necessary.
- Tracker changed from Issue to Story
- Subject changed from yum repo configuration - need to be able to toggle GPG to As a user I can set/update repo_gpgcheck and gpg_check options
- % Done set to 0
- Tags deleted (
Documentation)
- Status changed from NEW to ASSIGNED
- Assignee set to lmjachky
- Status changed from ASSIGNED to POST
- Sprint changed from Sprint 82 to Sprint 83
- Sprint changed from Sprint 83 to Sprint 84
- Status changed from POST to MODIFIED
- % Done changed from 0 to 100
- Sprint/Milestone set to 3.8.0
- Status changed from MODIFIED to CLOSED - CURRENTRELEASE
Also available in: Atom
PDF
.
Make gpgcheck and repo_gpgcheck configurable via the REST API
closes #6926