Support setting per-plugin configuration options in the config file #54
Assignees
Milestone
Comments
markgoddard
added a commit
that referenced
this issue
Nov 29, 2024
For some plugins it would be useful to be able to store configuration options in cofide.yaml. This change updates the plugin manager to support setting and retrieving per-plugin configuration keyed by the plugin name. The config can be set during Init or later using GetPluginConfig. A Struct protobuf message is used to allow for arbitrarily structured plugin config. Plugins can use the Struct directly or convert it to/from a more convenient native Go type. Fixes: #54
markgoddard
added a commit
that referenced
this issue
Nov 29, 2024
For some plugins it would be useful to be able to store configuration options in cofide.yaml. This change updates the plugin manager to support setting and retrieving per-plugin configuration keyed by the plugin name. The config can be set during Init or later using GetPluginConfig. A Struct protobuf message is used to allow for arbitrarily structured plugin config. Plugins can use the Struct directly or convert it to/from a more convenient native Go type. Fixes: #54 Depends-On: cofide/cofide-api-sdk#8
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
For some plugins it would be useful to be able to store configuration options in cofide.yaml. These may be arbitrarily structured. Several plugins may exist, and should each be able to add their own config.
The text was updated successfully, but these errors were encountered: