maif / wasmo Goto Github PK

https://docs.wasmer.io/registry/get-started

Current otoroshi template is well suited for wasm plugin such as access control, however it does not work for wasm backend.

We could either enrich current template with commented code for wasm backend, or add another specific Otoroshi wasm backend template.

When creating a plugin from a template from UI (for instance an Otoroshi request transformer), Wasmo create a plugin with an index.ts containing an execute function, while plugin.d.ts file declares that the plugin export a greet function.

• create link from plugin view that authorizes each receiver to edit it
• upon receiving, the plugin ID is added to the list of the user's plugins
• on removal, the plugin ID is removed from both lists

• https://github.com/MAIF/otoroshi-ts-types
• https://github.com/MAIF/otoroshi-go-types
• https://github.com/MAIF/otoroshi-rust-types

When compiling a typescript wasm plugin with wasmo 1.3.0, with an exported execute function, exported function name in wasm file isn't execute (as it was with 1.2.1 for instance) but always "greet".

• build

wasmo build 
  --path -p: path where is locate the source of the plugin to build
  --server -s: wasmo server to use

• init

wasmo init  // initialiaze a repository with the chosen type
  -- type -t [js/ts/go/rust/opa]
  -- name -n

• add .wasmo file under $HOME, with the token access and the wasmo server to join