> Hmm, I'm not really a fan of such a return type thing. My proposal would > be to have the old behavior (return a string) and then if somebody > really rather likes an array in different places, they could write a > wrapper method which would split the string for them.
+1 Well I think eventually we'll move to a better internal model supporting data types, for now sticking with key value and letting the data munging be handled further up the stack for lists is probably least disruptive for existing facter consumers. Paul
-- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
