-
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
chore(router) deprecate setting path handling v1 when router_flavor is traditional_compatible #9290
chore(router) deprecate setting path handling v1 when router_flavor is traditional_compatible #9290
Conversation
Good Job. But I think both |
@chronolaw Do you mean I saw that router_flavor only have three enum results kong/kong/conf_loader/init.lua Lines 438 to 440 in 9c990a7
And when kong/kong/db/schema/entities/routes.lua Lines 6 to 42 in 9c990a7
|
Now |
I think it is not very urgent for 3.0, because the new router only supports |
Yes, agree, not a blocker for 3.0, so no hurry for merging. |
bdc81f1
to
4fff6f3
Compare
8c9908e
to
4876a92
Compare
Co-authored-by: Datong Sun <dndx@idndx.com>
Co-authored-by: Datong Sun <dndx@idndx.com>
Co-authored-by: Datong Sun <dndx@idndx.com>
### Summary This fixes possible deadlock issue when worker is killed in middle of an event execution that also acquires locks or mutexes (and then never releases them). See: - KAG-4480 - KAG-4586 Signed-off-by: Aapo Talvensaari <aapo.talvensaari@gmail.com> (cherry picked from #13097) Co-authored-by: Aapo Talvensaari <aapo.talvensaari@gmail.com>
Summary
This PR
deniesusers from settingpath_handling=v1
when the Kong gateway is running withrouter_flavor=traditional_compatible
, as thepath_handling
feature is stepping into deprecation and path_handling v0 will be the default behaviour when composing upstream_uri.Discussed with the team and decide to only print deprecation log in the current version.
Full changelog
path_handling=v1
whenrouter_flavor
istraditional_compatible