Skip to content
This repository was archived by the owner on Nov 18, 2017. It is now read-only.

[Feature] Support Graphite input plugin configuration#16

Closed
noroute wants to merge 1 commit intojdowning:masterfrom
noroute:feature/graphite_input_plugin
Closed

[Feature] Support Graphite input plugin configuration#16
noroute wants to merge 1 commit intojdowning:masterfrom
noroute:feature/graphite_input_plugin

Conversation

@noroute
Copy link
Copy Markdown

@noroute noroute commented Dec 12, 2014

Enables support for:

  • database name
  • input port
  • disable plugin

closes #14, although it only supports one plugin at the moment.
Factor out common parts when supporting additional plugins.

Enables support for:
 * database name
 * input port
 * disable plugin

closes jdowning#14, although it only supports one plugin at the moment.
Factor out common parts when supporting additional plugins.
@jdowning
Copy link
Copy Markdown
Owner

Thanks for the PR. I decided to go a different route and drop the inifile usage in favor of a parameterized template. I believe I have solved the Graphite input-plugin configuration with #18. Let me know what you think.

@noroute
Copy link
Copy Markdown
Author

noroute commented Jan 24, 2015

It looks good so far. Will hook up our code that's already setting up influxdb instances for us and let you know next week.

The all-in-on template approach has the problem that every plugin/feature that is added adds more parameters (where there are already lots of). That's why I tried to encapsulate that.

@jdowning
Copy link
Copy Markdown
Owner

This project is no longer maintained. I recommend you check out golja/influxdb for an updated Puppet module for InfluxDB.

@jdowning jdowning closed this Nov 16, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Enable configuration of input plugins

2 participants