From 9144c26b1f2540c15c49af10e17e99899a975efd Mon Sep 17 00:00:00 2001 From: Rodolphe Breard Date: Wed, 24 Apr 2019 11:26:51 +0200 Subject: [PATCH] Allow not to have hooks or groups Before this commit, the configuration would be considered invalid if at least one hook and one group were not present. For obvious reasons, groups, which are simply an ordered aggregation of hooks, should be optional. On the other hand, hooks may seem mandatory since it is the only way to validate a challenge. However, this is false in some circumstances, for example in a test environment when running the client against a test server that does not perform challenge validation. https://github.com/letsencrypt/pebble#skipping-validation --- acmed/src/config.rs | 2 ++ 1 file changed, 2 insertions(+) diff --git a/acmed/src/config.rs b/acmed/src/config.rs index 6e3e095..d28b6f4 100644 --- a/acmed/src/config.rs +++ b/acmed/src/config.rs @@ -12,7 +12,9 @@ use std::path::Path; pub struct Config { pub global: Option, pub endpoint: Vec, + #[serde(default)] pub hook: Vec, + #[serde(default)] pub group: Vec, pub account: Vec, pub certificate: Vec,