[WIP] tooling: Add jsonschema dump of API (...cont)#15100
[WIP] tooling: Add jsonschema dump of API (...cont)#15100phlax wants to merge 1 commit intoenvoyproxy:mainfrom
Conversation
81e600a to
f631f5e
Compare
dd5be29 to
f1044f0
Compare
593c48a to
80d08dd
Compare
8ade5ba to
c3dd086
Compare
867d4a9 to
dcb0152
Compare
5649926 to
3b5ad80
Compare
dea371b to
dab2a1d
Compare
Signed-off-by: Ryan Northey <ryan@synca.io>
dab2a1d to
a08c8ec
Compare
|
This pull request has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in 7 days if no further activity occurs. Please feel free to give a status update now, ping for review, or re-open when it's ready. Thank you for your contributions! |
|
After rebasing to the latest main branch HEAD and making a slight modification to this PR branch to catch up with related changes such as #16618, #16496 and #18091, I have successfully generated a JSON schema for the Envoy configuration file based on the latest release version of Envoy (except for CryptoMbPrivateKeyMethodConfig extension). I am exploring to see if there is any other things that is blocking this improvement PR. |
|
@mmizutani its a while since i worked on this, unfortunately other priorities took precedence im trying to rem exactly what issues i hit - iirc generating the basic schema was not so problematic, but there were a few additinal hurdles to making it work with vscode i would be happy to review and/or help with this effort so feel free to ping me if you raise a PR |
|
Clearing myself from assignee until we have a PR ready for review, thanks. |
continuation of closed PR #13254
very WIP!
Commit Message:
Additional Description:
Risk Level:
Testing:
Docs Changes:
Release Notes:
Platform Specific Features:
[Optional Runtime guard:]
[Optional Fixes #Issue]
[Optional Deprecated:]
[Optional API Considerations:]