letsencrypt / letsencrypt/boulder

Make cert-checker a long-lived process

Open
#5,488 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Go
Stars
5.8k
Forks
649
Avg merge
3d 23h
Merged PRs (30d)
24

Description

Currently it is invoked on a schedule (by what? how often?) and runs once then exits. For uniformity with other boulder services, it would be nice if cert-checker were a long-lived process, doing work on its own schedule, like ocsp-updater.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by identifying what currently invokes cert-checker and how often, then compare its lifecycle and scheduling with ocsp-updater. Done means cert-checker remains running and performs its work on its own schedule, consistently with the other Boulder services.

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.