caddyserver / caddyserver/certmagic
Higher-level storage implementations
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 5.6k
- Forks
- 354
- Avg merge
- 9d 23h
- Merged PRs (30d)
- 3
Description
What would you like to have changed?
Currently Storage is a pretty low-level key-value store API. However, some storage backends may benefit from higher-level information. For instance, a storage implementation which uses k8s secrets to store private keys needs to know which items are TLS private keys and which items are just metadata.
Why is this feature a useful, necessary, and/or important addition to this project?
This would allow one to implement new Storage implementations, e.g. one based on k8s secrets.
What alternatives are there, or what are you doing in the meantime to work around the lack of this feature?
It's possible to parse the format of names passed to Storage. Are these guaranteed to be stable?
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 reviewing the existing Storage API and the issue discussion to understand which higher-level information backends need and whether name formats are stable. Done means the project has an agreed API design that lets implementations distinguish TLS private keys from metadata, with the required behavior and compatibility expectations documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100