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
I hope APISIX can check that it is being referenced and prevent the delete operation. like Upstream.
bash-5.1# curl -X DELETE http://127.0.0.1:9180/apisix/admin/upstreams/1 -H 'X-API-KEY: edd1c9f034335f136f87ad84b625c8f1'
{"error_msg":"can not delete this upstream, route [5] is still using it now"}
The text was updated successfully, but these errors were encountered:
tao12345666333
changed the title
bug:
bug: APISIX did not check whether it was referenced when deleting PluginConfig
Dec 24, 2021
I don't know whether there are some other objects which also are not checked when the Admin API deletes them, if so, we can list them and decide whether to check the reference before deletion.
Issue description
When a
PluginConfig
is referenced by multipleRoutes
, it can still be deleted.I expect APISIX can handle it the same as
Upstream
.If an
Upstream
is referenced by multipleRoutes
, an error will be reported when deleting.Environment
apisix version
): 2.10.2uname -a
):nginx -V
oropenresty -V
):curl http://127.0.0.1:9090/v1/server_info
to get the info from server-info API):luarocks --version
):Steps to reproduce
Actual result
Successfully deleted PluginConfig.
Error log
.
Expected result
I hope APISIX can check that it is being referenced and prevent the delete operation. like Upstream.
The text was updated successfully, but these errors were encountered: