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

Fix: Expression route handling fix for Konnect and < v3.7.0 #118

Merged
merged 1 commit into from
Jul 31, 2024

Conversation

Prashansa-K
Copy link
Collaborator

Summary

v3.7.0 added changes to allow traditional route fields with expression routes, thus making expression router a superset of traditional router.
Ref: Kong/kong#12667
Thus, keys like regex_priority are not supported in versions lesser than 3.7.0.

Added a gating logic in state builder for the necessary changes and fixed tests.
Fix #1250

Full changelog

  • Added gating logic in state builder
  • Fixed tests for the same

Issues resolved

Fix #1250

Documentation

Testing

  • Unit tests
  • E2E tests
  • Manual testing on Universal
  • Manual testing on Kubernetes
  • Manual testing using deck with gateway versions 3.6.1.7 and 3.7.1.2

@Prashansa-K Prashansa-K requested a review from GGabriele July 31, 2024 08:09
@codecov-commenter
Copy link

codecov-commenter commented Jul 31, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 41.35%. Comparing base (e7e4f68) to head (3f999c9).

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #118      +/-   ##
==========================================
+ Coverage   41.23%   41.35%   +0.12%     
==========================================
  Files          75       75              
  Lines       10892    10895       +3     
==========================================
+ Hits         4491     4506      +15     
+ Misses       5937     5925      -12     
  Partials      464      464              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

v3.7.0 added changes to allow traditional route fields with
expression routes, thus making expression router a superset
of traditional router.
Ref: Kong/kong#12667
Thus, keys like regex_priority are not supported in versions
lesser than 3.7.0.

Added a gating logic in state builder for the necessary changes
and fixed tests.
Fix #1250
@Prashansa-K Prashansa-K force-pushed the fix/version-logic-for-expression-routes branch from 0972e1b to 3f999c9 Compare July 31, 2024 09:18
@Prashansa-K Prashansa-K merged commit 61fbc91 into main Jul 31, 2024
42 checks passed
@Prashansa-K Prashansa-K deleted the fix/version-logic-for-expression-routes branch July 31, 2024 11:06
@Prashansa-K Prashansa-K self-assigned this Jul 31, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

render adding "regex_priority" key to expression route resulting sync to fails
3 participants