Current Behavior
In Standalone mode, APISIX can start successfully when plugins are not enabled in the config.yaml file but are used in Route/Service resources. However, the plugins will not take effect.
Expected Behavior
- If a plugin is not enabled in
config.yaml, an error should be shown/thrown when that plugin is used in resources such as Routes or Services.
- Whether or not to allow APISIX to start should be discussed.
Error Logs
No response
Steps to Reproduce
- Run APISIX in Standalone mode (https://docs.api7.ai/apisix/production/deployment-modes#standalone-mode)
- Use Standalone File-Driven mode
- Remove/Disable
key-auth plugin (as an example)
- Enable
key-auth plugin in apisix.yaml file
routes:
-
uri: /hello
plugins:
key-auth:
upstream:
nodes:
"10.244.1.5:1980": 1
type: roundrobin
#END
- Start APISIX successfully
Why
If a developer believes the Auth plugin is enabled but it actually fails to work, this could create potential security issues based on current behaviour.
Environment
- APISIX version (run
apisix version): 3.13
Current Behavior
In Standalone mode, APISIX can start successfully when plugins are not enabled in the
config.yamlfile but are used in Route/Service resources. However, the plugins will not take effect.Expected Behavior
config.yaml, an error should be shown/thrown when that plugin is used in resources such as Routes or Services.Error Logs
No response
Steps to Reproduce
key-authplugin (as an example)key-authplugin inapisix.yamlfileWhy
If a developer believes the Auth plugin is enabled but it actually fails to work, this could create potential security issues based on current behaviour.
Environment
apisix version): 3.13