Feature Request: nebula-service -test -config should warn about unknown keys and stuff in config yaml

[johnmaguire]

Discussed in #1142

^{Originally posted by fooryo May 9, 2024}
Idea came from a typo on a yml file.
My yaml was like:

lighthose:
  [...]
  hosts:
    - stuff in here

but nebula-service -test -config host.yml just told me:
WARN[0000] No lighthouse.hosts configured, this host will only be able to initiate tunnels with static_host_map entries

I know that the message is self explanatory but could be and idea that it reports also something like
there is no lighthose on nebula config yaml schema or lighthose key is not an expected key?

A json/yaml schema could also help with the fact that a lighthouse config should not have any lighthouse.hosts in the yaml ( I didnt research why tho ) and helps with a manual writing of such config files.

Thanks

[Akhil-2020171]

is anyone working on this? if not I can work on this FR.

[johnmaguire]

@Akhil-2020171 AFAIK, nobody is working on this, but it's not straightforward. We do not currently use any sort of struct or definition of the config file. The code will search for certain keys during runtime. There is currently no list of "valid keys" that we can test against. So I think there is really a rearchitecture of the config system that needs to happen for this task.