Permit to import multiple gpgkey for dnf
Open
Nobody has claimed this yet.
Feature
needs-triage
- Dominant language
- Python
- Stars
- 15.7k
- Forks
- 5.6k
- Avg merge
- 2d 44m
- Merged PRs (30d)
- 80
Description
Is your feature request related to a problem? Please describe.
Here is my .repo file:
[fluent-package-lts]
name=Fluentd Project
baseurl=https://packages.treasuredata.com/lts/5/redhat/$releasever/$basearch
enabled=1
gpgcheck=1
gpgkey=https://packages.treasuredata.com/GPG-KEY-td-agent
https://packages.treasuredata.com/GPG-KEY-fluent-package
I need 2 gpg keys on this.
But currently, the documentation doesn't mention the possibility of this.
Describe the solution you'd like
make gpgkey either str | list[str]
foo:
pkgrepo.managed:
- humanname: Personal repo for foo
- baseurl: https://mydomain.tld/repo/foo/$releasever/$basearch
- gpgcheck: 1
- gpgkey:
- https://my.repo.url/RPM-GPG-KEY-myrepo
- https://my.repo.url/RPM-GPG-KEY-myrepo2
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the pkgrepo.managed entry point and trace how the dnf-specific gpgkey value is currently parsed and passed through. Confirm how repeated keys are represented, then update the relevant documentation and tests so both a single key and multiple keys are accepted and verified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- devops
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100