configure function is not called when plugin configuration changes

[CatbirdBasil]

Is there an existing issue for this?

• I have searched the existing issues

Kong version ($ kong version)

2.8.4.11

Current Behavior

I'm writing my Custom plugin. I set up configure callback like so:

function MyPlugin:configure(configs)
  -- Implement logic for the configure phase here
  --(called whenever there is change to any of the plugins)
  kong.log.err("configure")
end

And when I start kong container I try to change configuration of my plugin, for example like so:

PATCH http://10.100.52.6:8001/plugins/1c290177-7956-4745-9946-66b7672ff59d
{
  "name": "my-plugin",
  "config": {
    "limits": {"max_buffer_size": 42430}
  },
  "enabled": true
}

But the log message inside the callback is never printed.

I might be getting the way it works wrong and in such case sorry, but that's as much as I could understand from the documentation here Implementing Custom Logic

Expected Behavior

I expect log message inside configure callback to be printed once I execute:

PATCH http://10.100.52.6:8001/plugins/1c290177-7956-4745-9946-66b7672ff59d
{
  "name": "my-plugin",
  "config": {
    "limits": {"max_buffer_size": 42430}
  },
  "enabled": true
}

Steps To Reproduce

1. Setup dummy custom plugin that only logs each phase/callback in handler.lua
2. Add plugin configuration field to schema.lua
3. Start kong with plugin available
4. Add plugin configuration
5. Change plugin configuration
6. Expect to see logs for configure phase

Anything else?

No response

[xianghai2]

Hi @CatbirdBasil ,

You may need to enable the custom plugin, uncomment following line of kong.conf.default ( or kong.conf ):

   #plugins = bundled 

Change it to:

   plugins = bundled,my-plugin

Then, start Kong with kong.conf.

[CatbirdBasil]

Hi, I already did that. Other callback are working fine like access or header_filter

[Water-Melon]

Unfortunately, the configure phase handler was involved in version 3.5.0.0.
https://docs.konghq.com/gateway/changelog/#core-19

[github-actions]

This issue is marked as stale because it has been open for 14 days with no activity.