[Question] How to reload plugin with new wasm file?

[fangzhengjin]

[Question] How to reload plugin with new wasm file?

[nilslice]

@fangzhengjin - which SDK are you using?

Also, what are you hoping to preserve by reloading a plug-in? If there's nothing about the previous plug-in needed, you should just create a new plug-in with the new wasm.

depending on the SDK you may also want to free the previous plug-in.

[fangzhengjin]

@fangzhengjin - which SDK are you using?

Also, what are you hoping to preserve by reloading a plug-in? If there's nothing about the previous plug-in needed, you should just create a new plug-in with the new wasm.

depending on the SDK you may also want to free the previous plug-in.

I use Rust SDK.
I want to upgrade the plugin without ending the main process and replace the WASM file. For upper users, they are still the same plugin.
I saw that Rust SDK provided some running methods, but they were all marked as unsafe, and lack of detailed explanation and use examples. Should I use them?

[fangzhengjin]

Maybe extism can provide a way to upgrade the plugin?
Block new plug-in call requests during the upgrade process, clean up old plug-in resources and resume plug-in call execution after the upgrade.

[mhmd-azeez]

I want to upgrade the plugin without ending the main process and replace the WASM file. For upper users, they are still the same plugin.

Can you elaborate on that please?

[fangzhengjin]

I want to upgrade the plugin without ending the main process and replace the WASM file. For upper users, they are still the same plugin.

Can you elaborate on that please?

I plan to plug-in some system functions and dynamically load them into the system. At this time, a single plug-in will be upgraded, but the main service will not be shut down.
Just like the Jenkins plug-in system, I can modularly update system functions online without restarting the service. For users, they have no perception. The only place where lags may occur is the blocking of requests during plug-in upgrades. New call requests and uninstalling old plug-ins, loading new plug-ins, and resuming blocked requests. If the operation goes smoothly, the user should not notice anything.

[neuronicnobody]

@fangzhengjin you should just be able to instantiate a new Extism Plugin and replace it with the old one as @nilslice suggested above. There shouldn't be a need to restart your service to do this.

Can you share a bit more about your architecture? (e.g., is this a multi-threaded app where different threads are sharing the Plugin object)