Currently plugin Configure interface accepts string map of key=value pairs taken directly from the Plugins.<name> configuration parameter.

There are several drawbacks with this approach:

• complex configuration can be supported only by encoding it into key names
• to access common parameters (timeout) plugin must directly access global agent configuration
• no built in (through tags) validation, default values

The idea is to change Configure parameter to interface{} which plugin would unmarshal into own configuration structure using Unmarshal method from conf package.

The parameter would contain a tree structure of configuration nodes (something like this is already used by configuration parser internally), but it would be better to hide the internal implementation by passing interface{}. All common parameters would be added to this tree structure under Common node.

Plugins would need to define their own options structure and embed the common options structure:

type Options struct {
   conf.Common
   // plugin options
}