forj-oss/goforjj

A go module to facilitate building a FORJJ plugin

goforjj's Issues

Find a way to provide plugin output as flow data to forjj

genapp: Difficult to change and set proper socket filename.

forjj through goforjj use <plugin>.yaml: /plugin: <value> to connect to the proper socket.

If we created a new plugin with a wrong name, the cli.go is generated and will never be updated if we do not remove it, before a go generate

So, even if we change <plugin>.yaml, forjj will take care of it, but not the plugin until we change manually the cli.go in load_plugin_def function

We need forjj and plugins to be more coherent.
The rule should be:

• if <plugin>.yaml: /runtime/serviice/socket:<value> is set, use it in both forjj and the plugin.
• if not set, use <plugin>.yaml: /plugin: <value> in both forjj and the plugin.

Deliver filter functions on data to transmit

When forjj get plugin definition, it provides the value (from Forjfile or cli), or a default value defined by the plugin.

Sometimes, those fields requires to be filtered so update the value to something acceptable by the plugin.

This is not a syntax verification which is normally already implemented through RegExp.

Filter example:

• ToLower: this function will downcase of the value to transmit to the plugin by Forjj.

This way, the filter is applied by forjj as defined by the plugin and do not require to update the plugin and simplify it.

Jenkinsfile missing

Automatically hide secrets in logs by default.

Applied to plugins or core

genapp do not break if .sock already exist.