On Nov 29, 2009, at 6:18 AM, Ohad Levy wrote: > If it happened to you before that someone broke your manifest > because of simple change (e.g. didnt test it on all hosts/classes > external nodes ... combinations) this tool might be useful for you. > > the idea is very simple, just try to compile the manifest based on > customized facts, classes, environments and external nodes > parameters (if you use it) . > You need to run this script only were you develop your manifests > (e.g. your puppetmaster), there is no need to try out a puppet run > on each and every system type that you have. > > You might also find it useful to run this script in some sort of a > cron or via a repo hook, to find out any broken manifests running > around.. > > This script was originally written by a colleague of mine (Paul > Kelly), however, I've adjusted it to hopefully common usage. > > Its brand new, so any comments / improvements (which I'm sure there > are plenty) are welcomed.
This is definitely very cool. It seems a bit limited because it actually runs the whole configuration, but I like it. It should definitely be straightforward to extend it to use a given host's Facts. You might also be able to get some inspiration on how to use the internal APIs by looking at puppet-test, which covers most of these bits using the internal APIs. -- I wanna hang a map of the world in my house. Then I'm gonna put pins into all the locations that I've traveled to. But first, I'm gonna have to travel to the top two corners of the map so it won't fall down. -- Mitch Hedberg --------------------------------------------------------------------- Luke Kanies | http://reductivelabs.com | http://madstop.com -- 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.
