tokers commented on code in PR #356: URL: https://github.com/apache/apisix-helm-chart/pull/356#discussion_r984352082
########## charts/apisix/README.md: ########## @@ -154,6 +154,48 @@ Default enabled plugins. See [configmap template](https://github.com/apache/apis | `extPlugin.enabled` | Enable External Plugins. See [external plugin](https://apisix.apache.org/docs/apisix/next/external-plugin/) | `false` | | `extPlugin.cmd` | the command and its arguements to run as a subprocess | `{}` | +### wasm plugin parameters + +| Parameter | Description | Default | +|---------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------| +| `wasmPlugins.enabled` | Enable Wasm Plugins. See [wasm plugin](https://apisix.apache.org/docs/apisix/next/wasm/) | `false` | +| `wasmPlugins.plugins[].name` | Set wasm plugin name | `""` | +| `wasmPlugins.plugins[].priority` | Set wasm plugin priority | `7999` | +| `wasmPlugins.plugins[].file` | Set path to wasm plugin | `""` | +| `wasmPlugins.plugins[].http_request_phase` | Set which http request phase for the plugin to run in | `access` | + +Note: + - the easiest way to to include your wasm custom plugin is to rebuild apisix image with those custom plugin included within directory you define and later on gets referenced to `wasmPlugins.plugins[].file` Review Comment: ```suggestion - the easiest way to include your wasm custom plugin is to rebuild the apisix image with those custom plugins included within the directory you define and later on gets referenced to `wasmPlugins.plugins[].file` ``` -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
