First, apologies if this is a FAQ: a few weeks of searching and reading hasn't uncovered anything particularly helpful. I'll be happy to summarize the results in a blog post or some more official place.
I'm having a hard time figuring out how best to develop and test changes to Puppet manifests. First, I don't have any way to test a change aside from tossing it on the server and running puppetd --test --noop on a potentially-affected client. Fundamentally, this is testing puppet's function mapping [ facts, manfiests, files ] => actions, and I would love to have a way to run that function without requiring a full, distributed puppetmasterd/puppetd setup, replete with correct facts on the client. Is there another way? Second, I'm working on refactoring our puppet configuration, and in so doing it would be best to ensure I haven't unexpectedly changed any resources. Is there any machine-parsable way of seeing the set of resources that result from a particular manifest and set of facts? Thanks for any pointers! Dustin -- 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.
