On 12/01/2009 01:47 PM, Nigel Kersten wrote:
> On Sun, Nov 29, 2009 at 6:18 AM, Ohad Levy<ohadl...@gmail.com> 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.
>
> No-one else tried this out? It's really quite cool.
I immediately added it to my todo list, but unfortunately I'm low on round
tuits right now...
> Ohad, I noticed you have /etc/puppet/manifests/site.pp hard-wired
> there. We actually serve our manifests out of a different location, so
> I had to do a minor tweak to get that working.
>
> It's a shame we can't impersonate architectures though... I'd love to
> be able to simulate catalog runs of a Mac client on a Linux continuous
> build server.
Well, all of that architecture stuff keys off of facter, right? How hard
would it be to serialize the output of 'facter -p' and feed it to the puppet
run that does the core of the testing work?
--
Frank Sweetser fs at wpi.edu | For every problem, there is a solution that
WPI Senior Network Engineer | is simple, elegant, and wrong. - HL Mencken
GPG fingerprint = 6174 1257 129E 0D21 D8D4 E8A3 8E39 29E3 E2E8 8CEC
--
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.
