Pluggability

[alexec]

Summary

Issues:

• Workflow lifecycle hook plugin #4355
• Plugin Template #5201
• Non-Golang plugins #7154
• Argo Server API v2 #7177
• Plugin install and uninstall CLI command #7710
• User interface plugins #6945
• Custom artifact repository plugins #5862
• Workflow notifications, e.g. Slack/Email when workflow finishes #6867
• Workflow and Template status change notification/trigger using Lifecycle Hook #7073
• Is there a hook for enter for template? #6313
• Archive to artifact repository #4162
• Support for Hadoop file format types when reading/writing artifacts: ORC, AVRO, Parquet #4163
• Visualizations in the Argo UI #7743

Related:

• Argo Workflows Core (aka "headless") #6615
• Argo CLI plugins #4158

---

Message from the maintainers:

Impacted by this bug? Give it a 👍. We prioritise the issues with the most 👍.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[agilgur5]

WASM / WASI could be a huge boon for plugins as it allows for code from almost any language to be executed in a secure, sandboxed way.

There is already the WASM Executor plugin, but we could potentially have built-in support for it and utilize WASM in several different places, including in the Controller and Server themselves, not just in ephemeral executors.

We could detect a WASM binaries on the filesystem and load them for different plugins, so a user could then have a custom image or volume mount with their binaries.

Implementation-wise, there do exist some great tools for this already, Exitsm in particular is an SDK for WASM-powered plugin systems and has an existing Go SDK.