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
{{ message }}
This repository was archived by the owner on Nov 18, 2017. It is now read-only.
There is currently no way to enable input plugins (cp. #12).
@justindowning Do you already have an idea on how that should be implemented? I'd be happy to work on that and submit a PR.
The major problem I see is how to cleanly allow users of the puppet module choose which plugins to enable and pass parameters for the different plugins. Modeling everything as a param would hugely increase the param space.
My intuitive solution sketch:
have a generic 'define' that represents one plugin entry with attributes
Usage would look like this:
include influxdb
influxdb::input_plugin {'collectd':
database => 'db1',
}
Note that as a consequence input plugins would not be disabled by just deleting the instantiation of the define. You'd need to explicitly instantiate it with something like 'ensure => absent'. Do you thinks this should be automatic?
There is currently no way to enable input plugins (cp. #12).
@justindowning Do you already have an idea on how that should be implemented? I'd be happy to work on that and submit a PR.
The major problem I see is how to cleanly allow users of the puppet module choose which plugins to enable and pass parameters for the different plugins. Modeling everything as a param would hugely increase the param space.
My intuitive solution sketch:
Usage would look like this:
Note that as a consequence input plugins would not be disabled by just deleting the instantiation of the define. You'd need to explicitly instantiate it with something like 'ensure => absent'. Do you thinks this should be automatic?
What do you think of the overall approach?