Add a new command action: verify

[meineerde]

Welcome

• Yes, I'm using a binary release or the library within the two latest releases.
• Yes, I've searched for similar issues on GitHub and didn't find any.

Detailed Description

It would be helpful to have a command which only verifies the configuration file against the schema and possibly any additional required rules (e.g. to ensure that there are any certificates or challenges defined). e.g. lego verify.

This new command should return a non-zero exit code if the config file is not valid.

It could be used to ensure that a given configuration file is syntactically and semantically valid before attempting to actually use the config file and without having to resort to manual validation with JSONSchema (as proposed in #3171).

I'd like to use this command to verify a generated configuration file as part of configuration management in order to outright reject invalid generated configuration files from being used in a live environment.

Effective version of lego

v5.3.1

How do you use lego?

Binary

In which context are you using lego?

Personal and professional use

🌱 Supporting the Maintainers

• Yes, I find this project useful, and I appreciate the work done by the maintainers.
• Yes, I have starred this repository to help others find it.
• Yes, I have sponsored this project to keep the project stable and maintained.

Confirmation

• Yes, I've included all the information above (version, usage, etc.).

[ldez]

When I created the V5, I through about that.

First, you have to know that the loading of the configuration is more complex than loading a file.
Technically, lego load the file into a structure, after that the defaults are applied, and the configuration is validated.

For me, a "validation" is different than a "verification":

• The "validation" requires a structurally valid configuration file (YAML), because this is a functional/business validation (ex: is the challenge referenced inside the configuration of a certificate defined?)
• The "verification" happens on the raw file without concrete knowledge of the business, and verifies only the structure of the file.

If the YAML file is invalid (JSONschema) the command will already, in 90% of cases, be rejected by the "validation" process.

So, my through was that a "verification" against the JSONSchema was not needed as the file was already "validated".

But I didn't through to a use case as yours with generated configuration file 🤔

If I add a "verify" command, this command will have to do the "verification" and the "validation".