rtl: make extraConfig
recursively mergeable
Previously, when merging different definitions of `extraConfig`, only the top-level attrset was merged. Example: The two separate settings nodes.lnd.extraConfig.Settings.userPersona = "MERCHANT"; nodes.lnd.extraConfig.Settings.logLevel = "DEBUG"; were previously merged into nodes.lnd.extraConfig.Settings = { logLevel = "DEBUG" }; (The last definition has precedence.)
This commit is contained in:
parent
b76728a1ec
commit
5634f08873
|
@ -27,7 +27,7 @@ let
|
||||||
description = mdDoc "Enable the clightning node interface.";
|
description = mdDoc "Enable the clightning node interface.";
|
||||||
};
|
};
|
||||||
extraConfig = mkOption {
|
extraConfig = mkOption {
|
||||||
type = types.attrs;
|
type = with types; attrsOf anything;
|
||||||
default = {};
|
default = {};
|
||||||
example = {
|
example = {
|
||||||
Settings.userPersona = "MERCHANT";
|
Settings.userPersona = "MERCHANT";
|
||||||
|
@ -52,7 +52,7 @@ let
|
||||||
description = mdDoc "Enable swaps with lightning-loop.";
|
description = mdDoc "Enable swaps with lightning-loop.";
|
||||||
};
|
};
|
||||||
extraConfig = mkOption {
|
extraConfig = mkOption {
|
||||||
type = types.attrs;
|
type = with types; attrsOf anything;
|
||||||
default = {};
|
default = {};
|
||||||
example = {
|
example = {
|
||||||
Settings.userPersona = "MERCHANT";
|
Settings.userPersona = "MERCHANT";
|
||||||
|
|
Loading…
Reference in New Issue
Block a user