Describe the bug
When creating a north/south service, you can select if the plugin behind that service will be enabled by default or not from the GUI (or from the API).
If you create a service disabled at creation, then plugin_init is called for that plugin.
And even more strange the plugin initialized this way then seems to "disappear" without even a call to plugin_shutdown, which may result in memory leaks.
To Reproduce
Steps to reproduce the behavior:
Create a new fledge-south-hnz service from Fledge GUI with log level set to "debug" at startup (through START_LOG_LEVEL).
Uncheck the "Enable" box in the last menu of service creation.
Notice in the logs that plugin_init is called (that should not happen).
Enable the plugin in the options.
Notice in the logs that plugin_init is called again (as expected).
Notice in the logs that but plugin_shutdown was not called on that plugin between the two plugin_init (does not feel like the intended behavior).
Expected behavior
If we make the service disabled at creation, we expect the service configuration to be saved for when it will be enabled later, but no plugin to be initialized at all.
Describe the bug When creating a north/south service, you can select if the plugin behind that service will be enabled by default or not from the GUI (or from the API). If you create a service disabled at creation, then
plugin_initis called for that plugin. And even more strange the plugin initialized this way then seems to "disappear" without even a call toplugin_shutdown, which may result in memory leaks.To Reproduce Steps to reproduce the behavior:
plugin_initis called (that should not happen).plugin_initis called again (as expected).plugin_shutdownwas not called on that plugin between the twoplugin_init(does not feel like the intended behavior).Expected behavior If we make the service disabled at creation, we expect the service configuration to be saved for when it will be enabled later, but no plugin to be initialized at all.
Additional context