Plugin Hot Reload

[Ben8t]

Integrating a new plugin need a Kestra server restart. Being to load at runtime new plugins will allow better deployment experience.

• https://www.toptal.com/java/java-wizardry-101-a-guide-to-java-class-reloading
• https://github.com/elastic/elasticsearch/blob/main/server/src/main/java/org/elasticsearch/plugins/UberModuleClassLoader.java#L83
• https://github.com/quanla/classreloading/blob/master/src/main/java/qj/util/lang/AggressiveClassLoader.java
• https://github.com/quarkusio/quarkus/blob/main/extensions/google-cloud-functions/runtime/src/main/java/io/quarkus/gcp/functions/QuarkusHttpFunction.java#L21

[Ben8t]

Next idea : if user try to insert a plugin in his flow but the plugin is not in instance, then show a pop up to let user install the plugin.

[brian-mulier-p]

@Ben8t I don't see myself as a user adding a full task name (qualified name) before getting the popup. I think it would work only if we also have autocompletion on plugins not in our instance so I guess providing such feature requires autocompletion revamp.

Regarding this autocompletion revamp, how to handle simple users which do not have the ability to add new plugin to their instance ? 😔 For those users we probably want the current autocompletion and not the full one :/

[yuri1969]

Linking to #945 as they seem to be duplicates.