Add graphite_protcol parameter to config class #27
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Under the Puppet future parser/4.0 language, variables used in
templates can only come from the local scope, and/or be explicitly
scoped with the scope.lookupvar function.
This adds a graphite_protocol parameter to the config class so that
the @graphite_protocol variable referenced in diamond.conf.erb will
be in the local scope. Otherwise diamond.conf gets generated with
a blank GraphiteHandler/proto setting (when using the Puppet
future parser.)
Also updating the equals sign alignments, so all but line 10 is just
whitespace changes.