Skip to content
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

make sure that the LB Data JSON examples are always up to date in documentation #2291

Closed
cz4rs opened this issue May 22, 2024 · 0 comments · Fixed by #2305
Closed

make sure that the LB Data JSON examples are always up to date in documentation #2291

cz4rs opened this issue May 22, 2024 · 0 comments · Fixed by #2305
Assignees

Comments

@cz4rs
Copy link
Contributor

cz4rs commented May 22, 2024

A follow up to #2124 to avoid docs getting out of sync again. This should also help catching any accidental changes in the generated files.

What Needs to be Done?

  • add a reference LB Data JSON file
  • add a unit test / example that will generate LB Data JSON file and compare it with the reference
  • make sure that the example is checked with schema validator
  • embed the reference JSON file in vt/docs/node_lb_data.md
  • make sure the JSON Python validator stays up to date also by including the segment of code
thearusable added a commit that referenced this issue Jun 20, 2024
thearusable added a commit that referenced this issue Jun 25, 2024
thearusable added a commit that referenced this issue Jun 27, 2024
thearusable added a commit that referenced this issue Jun 27, 2024
lifflander added a commit that referenced this issue Jul 16, 2024
…s-always-up-to-date

#2291: Make LB data examples always up to date
cwschilly pushed a commit that referenced this issue Sep 20, 2024
cwschilly pushed a commit that referenced this issue Sep 20, 2024
cwschilly pushed a commit that referenced this issue Sep 20, 2024
cwschilly pushed a commit that referenced this issue Sep 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants