Hello all,
Regarding my question with automated data binding. Here is how we set this
via the yaml backend:
collectd::plugins::write_riemann::riemann_protocol: UDP
We tried to use this with the json backend, but this never gets populated
in the class:
{"collectd":
{"plugins":
{"write_riemann":{"riemann_protocol": "UDP"}
}}}
Is the format we try to use wrong?
Best regards,
Cristian Falcas
On Tue, Jul 22, 2014 at 4:00 PM, jcbollinger <john.bollin...@stjude.org>
wrote:
>
>
> On Monday, July 21, 2014 9:39:39 AM UTC-5, David Schmitt wrote:
>>
>> On 2014-07-21 15:00, jcbollinger wrote:
>> >
>> >
>> > On Monday, July 21, 2014 12:00:35 AM UTC-5, Atom Powers wrote:
>> >
>> > I think you should be able to send json to the yaml backend and it
>> > will work. I did some testing with hiera and had no problem with
>> > pure yaml, pure json, or a mix of the two.
>> >
>> >
>> > Yes, JSON is more or less a subset of YAML. I don't recall at the
>> > moment what prevents JSON from being a complete subset, the kinds of
>> > JSON structures you're likely to want to use for your external data
>> > should all be fine.
>>
>> JSON can only do simple values (string, number), lists and hashes. YAML
>> can additionally reference entities across the document (creating loops)
>> and do all sorts of other nasty things that rubyists found funny to put
>> into a serialization format.
>>
>>
>
> Yes, but that's beside the point. The question is not what YAML can do
> that JSON can't, but rather what JSON can do that YAML can't. YAML 1.2 is
> intended to be a superset of JSON, but (I had remembered reading) doesn't
> succeed 100% in that. It turns out that the difference I was thinking of
> is that the JSON specs don't actually *require* mapping keys to be unique
> (JSON only suggests that keys be unique), whereas YAML does require unique
> keys (http://yaml.org/spec/1.2/spec.html#id2759572). In practice, that
> may be a distinction without a difference.
>
>
> John
>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to puppet-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/puppet-users/f3f7959f-5dac-4b85-b7ee-ca746460adc8%40googlegroups.com
> <https://groups.google.com/d/msgid/puppet-users/f3f7959f-5dac-4b85-b7ee-ca746460adc8%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
>
> For more options, visit https://groups.google.com/d/optout.
>
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/CAMo7R_cOmroL3D-H%2B30B%3DVTXJkM-LtRK5S0wbqaP46Q%3D2u6jHQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
