-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
refactor(db/schema): improve expression validation #10100
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good to go after renaming is done.
e17a2cc
to
023f4ff
Compare
03e3512
to
6b3d2ec
Compare
a42de10
to
570729b
Compare
@chronolaw Is this ready for review? |
Blocked by Kong/atc-router#39. |
@hbagdi Can you elaborate on the version compatibility concerns here as this refactor looks to keep the schema intact? |
No concerns @mikefero. |
None; the schema is intact (just moved) and only impacts validation of the expression router. All good here. |
@chronolaw Any blockers on this PR? |
Yes, It still wait the atc-router's new release. See Kong/atc-router#39. |
570729b
to
f771d3f
Compare
@hbagdi Taking this statement back now, it looks like we are removing a field. @chronolaw What is the reasoning for removing a field in f771d3f? This will have a negative impact on version compatibility with older data planes. |
No, the field OK, I will restore it. |
44a8a7b
to
141e494
Compare
875bbb1
to
67c2559
Compare
4e43a0d
to
7342f97
Compare
Summary
Why:
validate
API in atc-router could improve the validation performance.When the atc-router releases a new version, this PR will be ready to merge.
KAG-1524
Checklist
Full changelog
validate_entity_by_expression
and change entrancePATH_V1_DEPRECATION_MSG
traditional_compatible