Configuration Validator
Problem Statement
GitOps upgrade are failing because Helm custom values are incorrect. The goal is to develop a tool to make tests to limit the risk (e.g. schema issue).
Description
A tool for validating structured configuration files against a predefined templates (YANG or JSON Schema). The validator checks constraints like maximum number of elements in lists, required keys, and custom rules. These rules are defined in a YANG or JSON Schema provided by the user / customer and validated against given input files.
Supported Features
| Feature | Description |
|---|---|
| Schema Validation | Validates configuration files against a given YANG or JSON Schema |
| Supported Formats | Supports .json, .yaml, .yml, .xml, .ini and .properties formats |
| CI/Pipeline Integration | Pipeline (CI) integration with configurable config.json file |
| CLI Support | Alternative CLI-based tool with two modes: Direct mode via command-line flags and Interactive mode via CLI prompts |
| Built-in IETF Modules | Includes built-in IETF YANG modules (ietf-yang-types, ietf-inet-types, ietf-ip, ietf-interfaces) with no external provisioning required |
| Custom YANG Modules | Additional YANG modules can be added using the YANG_MODULES_PATH environment variable. All required modules placed in this path are imported before validation starts |
Validator Workflow
Project Details
Leader: DT (M.Thaker)
List of people/organization interested to join:
- Orange (E.Moniz, M.Richomme)
- X
Presentation: see WG06 May minutes for details
Hackathon Objectives
- Review current features
- Improve custom values validation
- Add features (comparison with config up&running before upgrade)