On Wed, Dec 2, 2009 at 2:47 AM, Nigel Kersten <nig...@google.com> wrote:
> 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. > I'll see what I can do about that ;) > > 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, the answer for this is - it depends :) the main problem here is not to override the facts (which must do anyway), but things that the puppet provider will force, e.g. an example error that you *might* get if you try it on another operating system (in this example a Solaris manifest on a Linux host) debug: Puppet::Type::Host::ProviderParsed: file /etc/inet/hosts does not exist Could not find a default provider for host nevertheless, it might work for your environment, but as you can see in this case, it generates a false alarm. Cheers, Ohad -- 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.
