> > * Because of complexity of how and when classes are interpreted, > > aren't variables often a tricky thing to play with if you are > > planning to change their values in later scopes? > > With the current tooling, I think the only real chance is to put all > "choosing values for variables which will influence my manifests" > functionality in an external nodes classifier which does proper, > flexible and organisation-specific lookups. > > HAving this, manifests and modules do have a greatly reduced need to > "change values in later scopes". >
I agree. > > * Lastly, perhaps this is still my OCD, but I'm still a fan of the > > style guide. Without it, I dont' think our manifests would be as > > clean and legible as they currently are. > > +1 :) -- Digant C Kasundra <dig...@stanford.edu> Technical Lead, ITS Unix Systems and Applications, Stanford University --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@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 -~----------~----~----~----~------~----~------~--~---
