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 have 5 multiple instances of the same plugin (different config) applied to 5 different services. I was just testing the setup by disabling and enabling the plugin. After enabling the plugin again, pdk created a new instance #6 but did not delete the older instance. Is this expected? I see the following error logs when I enable the plugin again. Seems like it is unable to close the instance. This is not affecting anything, the requests are being forwarded correctly but unnecessarily kong is maintaining the older instances which are not being used.
@abhisheksharma2805 Just to double check when you mean enablding/disabling the plugin is it something
like attaching it to a Service then delete it? There might be a bug, let me try to reproduce.
@fffonion Yes, setting plugin.enabled = false or even deleting the plugin and re-attaching to the service is throwing this error. Basically I also see that updating any config parameter of the plugin it throws this error.
I have 5 multiple instances of the same plugin (different config) applied to 5 different services. I was just testing the setup by disabling and enabling the plugin. After enabling the plugin again, pdk created a new instance #6 but did not delete the older instance. Is this expected? I see the following error logs when I enable the plugin again. Seems like it is unable to close the instance. This is not affecting anything, the requests are being forwarded correctly but unnecessarily kong is maintaining the older instances which are not being used.
The text was updated successfully, but these errors were encountered: