Signing Service is not updated when signing key or signing script is updated
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 88
- Forks
- 66
- Avg merge
- 53m
- Merged PRs (30d)
- 1
Description
Version
pulp-operator:v1.2.0
Describe the bug
When signing key or signing script is updated, all Pods are restarted, but the signing service is not updated. Thus, it still uses the old signing key.
To Reproduce
Steps to reproduce the behavior:
Change on of the following:
- signing_scripts or signing_secret in the Pulp custom resource
- Update the Secret holding the content of signing_scripts or signing_secret
Expected behavior
A clear and concise description of what you expected to happen.
The signing service is updated, along with all repositories using that service.
Additional context
Add any other context about the problem here. Please provide links to any previous discussions via Discourse or Bugzilla.
I check the signing service via:
pulp signing-service list
and see that public_key and pulp_last_updated are not updated.
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 the Pulp custom resource handles signing_scripts and signing_secret changes, including updates to the Secrets that hold them. Use pulp signing-service list before and after changing either input to verify whether public_key and pulp_last_updated change. Done means the signing service and repositories using it reflect the updated signing material.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- backend, infrastructure, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100