On 04/15/2014 09:25 AM, Nikola Petrov wrote: > I haven't used catalog-diff but I > am suspecting that it might be a substitute for the rspec tests. Tell me
No. rspec allows you to implement unit tests to catch certain regression bugs. catalog-diff is rather concerned with integration testing (although you can use rspec for that as well). > does it provide the following: > > * Automatic runs through guard/rake/whatever on every commit to verify > that I am not breaking things like permissions on files You could do that, but compiling each of your nodes' catalog on every commit would be excessive. > * Does it work on the catalog semantic level or syntactic level - what > I mean by that is that if I have defined 4 files in a class each with > the same user/group/mode and I move those into default parameters for > the File resource in the scope - will it detect that I am not changing > anything? Absolutely. The mode of each file that the agent is supposed to manage is part of the catalog. A change in agent behavior is always prompted by a change in its catalog. > * Will I be able to test that things haven't changed once I move to > another puppet version - let's say the default mode for directories > change in the next major puppet version? Generally yes, though at PuppetCamp I heard that catalog-diff had issues with a certain release. I believe that a given catalog-diff version may not work with both your old and new puppet release. But apparently it's possible to coerce the catalog output into a diffable format if push comes to shove. Cheers, Felix -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/534D138D.1060102%40alumni.tu-berlin.de. For more options, visit https://groups.google.com/d/optout.
