Ability to use WASM runtime in actions

[davidferlay]

Current

• Action commands can define runtime to be either plugin or container (and soon shell/host too) to be executed either as go code, in container or locally.

Expected

• Plugin commands should be able to be executed as wasm binary on host
• This can have several advantages for actions commands: performance, portability/compatibility, security/isolation

[davidferlay]

Just thought of the perfect candidate: our ansible-based deploy action. It's currently running as a standard local action, with container runtime. It means that wherever we need to run run it, docker socket (or k8s soon) should be available.

However if we can turn this action into a wasm, we don't need to rely on any container runtime anymore. Which will be game changer 🚀

[lexbritvin]

It definitely won't fit ansible scenarios as WASM is intended to run in sandbox and doesn't allow to access external executable.
We need to define the expected use-case for wasm.