Current Behavior
Plugins from plugin_config override the plugins in the route.
Expected Behavior
The behavior should be the same as the plugins from services, which do not take effect when there are plugins with the same name in the route.
Let's make the behavior consistent in the V3.
Error Logs
No response
Steps to Reproduce
See
|
for name, value in pairs(plugin_config.value.plugins) do |
|
route_conf.value.plugins[name] = value |
|
end |
Environment
- APISIX version (run
apisix version): master
- Operating system (run
uname -a):
- OpenResty / Nginx version (run
openresty -V or nginx -V):
- etcd version, if relevant (run
curl http://127.0.0.1:9090/v1/server_info):
- APISIX Dashboard version, if relevant:
- Plugin runner version, for issues related to plugin runners:
- LuaRocks version, for installation issues (run
luarocks --version):
Current Behavior
Plugins from plugin_config override the plugins in the route.
Expected Behavior
The behavior should be the same as the plugins from services, which do not take effect when there are plugins with the same name in the route.
Let's make the behavior consistent in the V3.
Error Logs
No response
Steps to Reproduce
See
apisix/apisix/plugin_config.lua
Lines 67 to 69 in 5dee1a4
Environment
apisix version): masteruname -a):openresty -Vornginx -V):curl http://127.0.0.1:9090/v1/server_info):luarocks --version):