You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are several plugins like http output or file output that do not use codecs but the configuration allows user to define it. But having an open issue is not enough visibility for users!
Should a method similar to workers_not_supported be added to the base.rb class ad called from the register method of the plugins lacking codec support or do you see another way ?
The text was updated successfully, but these errors were encountered:
I think we should add another macro similar to the way were are defining the plugin config option.
The macros would alllow us to trap problems when we are parsing the config file (with or without using --configtest)
There are several plugins like http output or file output that do not use codecs but the configuration allows user to define it. But having an open issue is not enough visibility for users!
Should a method similar to
workers_not_supported
be added to the base.rb class ad called from the register method of the plugins lacking codec support or do you see another way ?The text was updated successfully, but these errors were encountered: