Adding YAML examples to developers wasm filter plugin docs. Fixes #1768.#1769
Conversation
| WASM_Path /path/to/built_filter.wasm | ||
| Function_Name super_awesome_filter | ||
| accessible_paths .,/path/to/fluent-bit | ||
| accessible_paths /path/to/fluent-bit |
There was a problem hiding this comment.
Just checking this change, is the original one a comma separated list with . allowing you to be path agnostic @cosmo0920 or is it just a typo?
There was a problem hiding this comment.
It isn't typo. Just including for the current working directory.
However, this should be removed if we pursue the rigid permission list approach.
Sometimes, I put Wasm programs into /path/to/fluent-bit/build directory and run fluent-bit in /path/to/fluent-bit/build directory. So, if we remove the magic . period symbol, we need to write the actual path of the place that contains the actual Wasm programs.
There was a problem hiding this comment.
Let's add that info to the docs then I think, at least call it out in the example here
There was a problem hiding this comment.
Ok, so I will add some text to refer to the fact that fluent bit needs to run from the same directory as the '/path/to/built_filter.wasm' file (aka the 'wasm_path').
…am app location. Signed-off-by: Eric D. Schabell <eric@schabell.org>
…ent#1768. (fluent#1769) * Adding YAML examples to developers wasm filter plugin docs. Fixes #fluent#1768. Signed-off-by: Eric D. Schabell <eric@schabell.org> * Added comment for accessable_path and running Fluent Bit from the wasam app location. Signed-off-by: Eric D. Schabell <eric@schabell.org> --------- Signed-off-by: Eric D. Schabell <eric@schabell.org> Signed-off-by: Tom <yao.lin@siemens.com>
Adding YAML examples to developers wasm filter plugin docs. Fixes #1768.