5e1bc3b501
Replace the current three-piece setup (enum of feature variables, map of feature vars to default values, and autogenerated bidirectional maps of feature variables to and from strings) with a much simpler one-piece setup: a single struct with one boolean-typed field per feature. This preserves the overall structure of the package -- a single global feature set protected by a mutex, and Set, Reset, and Enabled methods -- although the exact function signatures have all changed somewhat. The executable config format remains the same, so no deployment changes are necessary. This change does deprecate the AllowUnrecognizedFeatures feature, as we cannot tell the json config parser to ignore unknown field names, but that flag is set to False in all of our deployment environments already. Fixes https://github.com/letsencrypt/boulder/issues/6802 Fixes https://github.com/letsencrypt/boulder/issues/5229 |
||
|---|---|---|
| .. | ||
| test | ||
| README.md | ||
| cache.go | ||
| cache_test.go | ||
| prod_aia.go | ||
| stale.go | ||
| stale_test.go | ||
| stats.go | ||
| test_aia.go | ||
| verify.go | ||
| verify_test.go | ||
| wfe.go | ||
| wfe_test.go | ||
README.md
WFE v2
The wfe2 package is copied from the wfe package in order to implement the
"ACME v2" API. This design choice
was made to facilitate a clean separation between v1 and v2 code and to support
running a separate API process on a different port alongside the v1 API process.