letsencrypt / letsencrypt/boulder
Consolidate CT log logic in the publisher
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 5.8k
- Forks
- 649
- Avg merge
- 3d 23h
- Merged PRs (30d)
- 24
Description
Currently we have the CT group/sharding etc logic split across the RA, the ctpolicy package, and the publisher. This has no real benefit and makes understanding the logic rather complicated as you have to jump around a number of different components and understand the RPC boundaries that requires.
Instead we should just consolidate all of the logic into the publisher, which makes sense as it's always been intended as the centralized authority for CT stuff.
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
Map the CT group and sharding logic across the RA, the ctpolicy package, and the publisher, including the RPC boundaries between them. Done means the CT logic is consolidated in the publisher and the redundant cross-component split is removed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend, security
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100