-
Notifications
You must be signed in to change notification settings - Fork 814
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Validate yaml configuration with a schema #929
Comments
Do you think that logical conflicts such as #920 is within a scope of this issue? |
Interesting point. Yes, I think this kind of configuration limitations also should be described and validated declarative using json schema (e.g. at some point have |
Currently all the user-facing configuration is validated manually (sometimes on demand). So far it worked due to careful approach, but I think it's obvious that centralized declarative verification (using something like jsonschema) would be much less error prone and more convenient.
At the same time, since it potentially could be a breaking change to introduce such validation right away, it probably makes sense to report all the validation errors as warnings as the first step.
The text was updated successfully, but these errors were encountered: