letsencrypt / letsencrypt/pebble
HTTP Management Interface
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 787
- Forks
- 176
- PR merge metrics
- No merged PRs in 30d
Description
Discussion on https://github.com/letsencrypt/pebble/pull/39 indicated that there are users who would find it valuable to be able to inject test data into Pebble to help support integration testing with an ACME client.
Similarly, in https://github.com/letsencrypt/boulder/issues/2697 there was a desire for a way to signal "Reject the next n requests as if they had a badNonce".
Pebble should offer a basic HTTP "admin"/"test" interface on a different path/port than the ACME API that can be used to do management tasks like the two listed above.
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 Pebble’s existing ACME API and the linked discussions in the pull request and Boulder issue. Define the separate HTTP management interface and its behavior for injecting test data and rejecting the next n requests as badNonce; done means both management tasks are available without changing the ACME API and are covered by tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- api, testing
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100