Ability to add signing service for other Repositories
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 88
- Forks
- 66
- Avg merge
- 53m
- Merged PRs (30d)
- 1
Description
Is your feature request related to a problem? Please describe.
I am trying to add a Debian repo, I have signing service created for collection and containers but I am unable to create a signing service with the Apt class.
Describe the solution you'd like
It would be nice if the operator could read additional secrets and create those signing services.
Describe alternatives you've considered
Setting hosts to ignore gpg keys.
Additional context
There might be something I am missing, but this seems to be missing.
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 by tracing how signing services are created for collection and containers, then compare how the Apt class handles secrets. Identify the operator entry points for reading additional secrets; done means operators can create signing services for Debian repositories while existing collection and container behavior continues to work.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- devops, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100