[Feature] strict config validation

[SuperSandro2000]

Use case

I've run multiple times into issues because I've miss typed a config key name or forgot to copy a letter. Headscale should catch that and fail early in when loading the config and complain about keys it doesn't know.

Description

I am imagining something like json's DisallowUnknownFields() which complains if any field cannot be mapped into a struct.

Contribution

• I can write the design doc for this feature
• I can contribute this feature

How can it be implemented?

No response

[kradalby]

I agree, the whole config management is a bit of a pain, I particularly does not like that it can only be loaded and not easily dumped at the moment.