You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Kong file render generates legacy route "regex_priority" key when expression routes are used resulting that rendered file validation fails and file cannot be synched, resulting error
Error: 1 errors occurred:
while processing event: Update route debug_node_log-level failed: HTTP status 400 (message: "schema violation (regex_priority: unknown field)")
repro steps
Kong version 3.6.1.1, deck 1.35, linux
create declarative config with single service/route/plugin pointing to Kong itself
Kong file render generates legacy route "regex_priority" key when expression routes are used resulting that rendered file validation fails and file cannot be synched, resulting error
repro steps
Kong version 3.6.1.1, deck 1.35, linux
create declarative config with single service/route/plugin pointing to Kong itself
render the declarative configuration.
deck file render kong-common*.yaml merge-routes.yaml -o render-kong-deck.yaml
deck file merge kong-common*.yaml merge-routes.yaml -o merge-kong-deck.yaml
rendered file contains "regex_priority" which is used with legacy routes.
Validation of rendered file fails.
Rendered file cannot be used to sync with Kong.
Merged file can be synched because it does not contain regex_priority key
Workaround - use kong deck patch to remove invalid key
cat render-kong-deck.yaml | deck file patch --selector="$..routes[*]" --value="regex_priority:" -o render-kong-deck.yaml
The text was updated successfully, but these errors were encountered: