Hi, I''m looking into using puppet master --compile to set up some tests. However it''s unclean how I can use this: - do I *need* to run this on the master? - what are the exit statuses that I need to catch? - why does it update /var/lib/puppet/yaml/node/<nodename>.yaml after such a run? Thanks, Rudy -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscribe@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
On Sunday, June 2, 2013 5:05:23 PM UTC-5, Rudy Gevaert wrote:> > Hi, > > I''m looking into using puppet master --compile to set up some tests. > However it''s unclean how I can use this: > > - do I *need* to run this on the master? >You need to run it on a system that has all the Puppet manifests and data for the requested catalog''s target node, and the Puppet master software. That makes it at least *a* master, even if it''s not *the* master. For your tests to yield relevant results, the system on which you compile catalogs must have the same manifests and data as the master, so if they are not the same system then you need to have some mechanism for keeping them synchronized. If the point is to test whether everything will compile correctly on the master, however, then there really is no fully-reliable alternative to testing it on the master.> - what are the exit statuses that I need to catch? >Others will have more specific information there, but I would expect to see status 0 if compilation is successful, else nonzero.> - why does it update /var/lib/puppet/yaml/node/<nodename>.yaml after > such a run? > >Whenever the master compiles a catalog, it writes a YAML serialization of it there, but I am neither prepared to nor interested in debating "why" it does so. John -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscribe@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Thanks for the feedback! -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscribe@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
On Tue, Jun 4, 2013 at 7:12 AM, jcbollinger <John.Bollinger@stjude.org>wrote:> - what are the exit statuses that I need to catch? >> > > Others will have more specific information there, but I would expect to > see status 0 if compilation is successful, else nonzero. >Not sure this is all that reliable, yes it will catch compilation errors, but a successfully generated catalog can still fail to even run on the client due to missing resource dependency. If you wish to compile a catalog and make some assertions about the results, rspec-puppet is the way to go. Nan -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscribe@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.