bug: PluginConfigId is not assigned to the route in case upstreams used instead of the backends #1577
Labels
bug
Something isn't working
triage/accepted
Indicates an issue or PR is ready to be actively worked on.
Issue description
I am using the ingress controller to create the following apisix resources:
The following definitions are used:
As result my configuration is applied to the apisix, but plugin config is not assigned to the route.
My assumption that issue is because of the bug in the following file: apisix_route.go, more precisely the following fragment
is only executed when
len(backends) > 0
(function translateHTTPRouteV2).I guess it should be applied both for case with backends and case with upstream, like mine.
Environment
Minimal test code / Steps to reproduce
Actual result
plugin_config_id is missed from the configuration
Error log
no error log, just incorrect behaviour
Expected result
plugin_config_id is properly assigned to the route
The text was updated successfully, but these errors were encountered: