letsencrypt / letsencrypt/pebble

Feature suggestion: allow setting a subset of configuration

Open
#297 1 comment 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement help wanted
Dominant language
Go
Stars
787
Forks
176
PR merge metrics
No merged PRs in 30d

Description

For my project I had to set a custom value for httpPort in pebble-config.json.

Currently in my custom JSON I need to specify the rest of the configuration as well:

{
  "pebble": {
    "listenAddress": "0.0.0.0:14000",
    "managementListenAddress": "0.0.0.0:15000",
    "certificate": "test/certs/localhost/cert.pem",
    "privateKey": "test/certs/localhost/key.pem",
    "httpPort": 80,
    "tlsPort": 5001,
    "ocspResponderURL": "",
    "externalAccountBindingRequired": false
  }
}

It would be convenient if I could omit all properties but the ones I need to modify. So my JSON would look like this:

{
  "pebble": {
    "httpPort": 80
  }
}

Pebble could pull the default values for the rest.

Contributor guide

No contributing guide indexed for this repository

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 locating the code that loads pebble-config.json and defines Pebble's default configuration. Check how the pebble properties are decoded, then verify that a JSON file containing only httpPort retains defaults for all omitted properties while existing full configurations continue to work.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
backend
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.