On 2013-03-07 10:48, Erik Dalén wrote:
I agree that it feels odd to put code inside data though. But it is a very effective way to reuse forge modules without having to modify them and not having to hardcode or duplicate a lot of data that can be looked up using some function.
To me the distinction "data vs. code" is not as interesting as that of "separation of concerns" - there are many sane use-cases for logic in "data". It is more important to think about the various concerns; how can a module be reused, how is it configured, how can data be reused (not having to specify the same item over and over), how can a module adapt (or be told to adapt) its behavior depending on the the presence of other modules, etc.
Regards - henrik -- You received this message because you are subscribed to the Google Groups "Puppet Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/puppet-dev. For more options, visit https://groups.google.com/groups/opt_out.
