Draft: conf data parser/validator reimplemenation (!6) · Merge requests · Knot projects / knot-resolver-manager · GitLab

GitLab now enforces expiry dates on tokens that originally had no set expiration date. Those tokens were given an expiration date of one year later. Please review your personal access tokens, project access tokens, and group access tokens to ensure you are aware of upcoming expirations. Administrators of GitLab can find more information on how to identify and mitigate interruption in our documentation.

Self sign-up has been disabled due to increased spam activity. If you want to get access, please send an email to a project owner (preferred) or at gitlab(at)nic(dot)cz. We apologize for the inconvenience.

Aleš Mrázek requested to merge internal-config-datamodel into master Aug 23, 2021

Implements #13 (closed)

YAML/JSON parser and data validator are now two separated modules. They are used to define two separated schemas.

SchemaParser + dataclass
- creates parser for incoming YAML/JSON data
- looser type definitions for attributes
- supports partial change of data
- specifies the structure of the configuration file
- specifies default values of attributes
- exports SchemaParse object to YAML/JSON
SchemaValidator
- creates transformation and validation schema
- type definitions for attributes shoul be more strict
- SchemaParser object serves as input parameter
- validation method for every SchemaValidator node must be implemented
- transformation method for any attribute
- input for Lua configuration template

Some examples can be found in schema_parser and schema_validator tests.