Allow signing services to be managed via the API
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 598
- Forks
- 168
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 86
Description
Today signing services have to be created by running a pulpcore CLI command. This is somewhat awkward in container-based environments. You have to either connect to the container to run the command or have some code when a container starts to run the command.
We do the latter but it means that in order to create a new signing service, we have to do a whole production deployment which can take days. Ideally, we'd like a way to create signing services through the API. Being able to create signing services through the API would make it easier for us to implement a strategy like Fedora's where we use a new signing key for each repo.
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 examining the existing pulpcore CLI command for creating signing services and the related API patterns. Add an API path that supports creating signing services, then verify that signing services can be created through the API as described in the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100