Open phlax opened 4 years ago
@phlax see prior art here in our various config tooling: https://github.com/envoyproxy/envoy/tree/master/test/tools and https://www.envoyproxy.io/docs/envoy/latest/install/tools/tools. See also related tickets here: https://github.com/envoyproxy/envoy/issues?q=is%3Aopen+is%3Aissue+label%3Aarea%2Froute_check_tool.
It would be great to unify all of these efforts where possible.
It would be great to unify all of these efforts where possible.
yep, thanks for refs
the config load tool does a bit more than static analysis so i think we would want to at least retain that functionality (edit: ...in terms of config linting. Ill try and spend some time to see what other tooling is there)
after a little more dev/research on this im wondering whether its possible/better to do this directly from protobuf - ie without the jsonschema step.
either way it would be good to publish the jsonschema to https://www.schemastore.org/json/ so existing jsonschema tooling beyond vscode can make use of it (touch #13254 #13078)
Hey @phlax, didn't realize you posted it here. I updated the site to now run against Envoy binaries with three different versions supported (1.16, 1.14, 1.12).
Hey @phlax, didn't realize you posted it here.
yep, i still think a static analysis tool could be useful, and was collating related info here
I updated the site to now run against Envoy binaries with three different versions supported (1.16, 1.14, 1.12).
cool, ive pointed a couple people towards it already
description
If we create
jsonschema
for validating envoyyaml
/json
config files (see #13078) we can potentially re-use the schema for acli
linter (and/or libs for python/js etc).This could eg be used to:
refs
13078 (vscode)
8837 (config validation)
13231 (move snippets to rst includes)
13167 (automate dumping of typed extensions)