On Apr 19, 2012, at 11:26 AM, Andrew Parker wrote: > So the main, sane, use case for inheritance is to set resource defaults. That > is the same thing I've heard from others, so at least people seem to agree on > that :)
Yep, that's all I used them for. >> Puppet could very desperately use a debugging compiler -- attach as a given >> node and output the streams which get one to the compiled catalog state. >> Show every assignment, every override, everything. > > Hmmm, that would be interesting. Might put out a lot of information, though, > which would make it hard to follow. Go to one of my apps, add some debug options to the end of the query and you'll get 20-30k lines of text depending on the transaction. When you are trying to solve something really wicked, nothing halfway will do the job. In a real debug, any action taken should be logged and viewable. It's only when actions aren't taken (like in Puppet's current selinux debugging) that debug becomes useless. -- Jo Rhett Net Consonance : consonant endings by net philanthropy, open source and other randomness -- 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.
