Brice Figureau <[email protected]> writes:
> On 28/05/10 12:46, Markus Roberts wrote:
>>> Comments?
>>
>> A few thoughts I had on first read through: Is this a use case for
>> hashes? Should it be a passthrough / override setup (so that the module
>> write can provide defaults for values the user does not provide)? At
>> what epistemological level is the data path determined?
>
> Luke mentioned yaml, so that external data are pure data. Using hashes
> would make our pure data more data in code than data.
If you forgive me saying it, I have not the faintest idea what you were
*trying* to convey here: YAML supports the hash as a basic data structure, so
this seems somewhere between meaningless and crazy to state.
So, I don't know what you were trying to say when you suggest that a hash is
somehow "less pure" as a data format than an array or a string, but your point
sure didn't get across to at least some of the audience.
Er, and perhaps it doesn't help my confusion that the existing extlookup tool
models exclusively a (single level) hash data structure, based on key in the
first column, and multiple additional named columns for each row...
Daniel
--
✣ Daniel Pittman ✉ [email protected] ☎ +61 401 155 707
♽ made with 100 percent post-consumer electrons
--
You received this message because you are subscribed to the Google Groups
"Puppet Developers" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/puppet-dev?hl=en.
