letsencrypt / letsencrypt/pebble
Cleanup pebble-challtestsrv HTTP API
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Go
- Stars
- 787
- Forks
- 176
- PR merge metrics
- No merged PRs in 30d
Description
It's pretty messy right now but we'll need to bump major versions to fix it.
In particular it probably makes sense to try and make one or two more general endpoints for adding mock DNS data instead of one per-type (set-cname, set-txt, set-servfail, etc).
Contributor guide
No contributing guide indexed for this repository
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 pebble-challtestsrv HTTP API and its existing per-type endpoints, including set-cname, set-txt, and set-servfail. Done means agreeing on a less repetitive endpoint design and documenting the major-version changes required to introduce it.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- api, testing
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100