Hi Wolf, see if this works for you
https://github.com/ripienaar/puppet-catalog-diff On Mon, Oct 21, 2013 at 12:25 PM, Wolf Noble <[email protected]> wrote: > Hi there, > > I realize this isn't quite a dev question, but I'm going to ask anyways :) > > my situation is that I'm trying to refactor a large module base that > doesn't have unit tests. > > when making changes, I want to verify that there are as few unanticipated > changes as possible.. > > our strategy to achieve this was to generate a catalog for our common node > types: > > puppet master --verbose --compile nodetype1 >nodetype1.catalog > puppet master --verbose --compile nodetype2 >nodetype2.catalog > … > > Then generate a graph from each type: > > puppet apply --graph --noop nodetype1.catalog > puppet apply --graph --noop nodetype2.catalog > > then make the changes and re-run… giving us the ability to inspect and > compare the catalogs with greater ease.. > > > The problem I'm encountering seems to be one of those can't quite get > there from here situations, and I'm somewhat stumped as to how to proceed. > > it seems that when puppetdb is in play, puppet master --compile does not > spit out a catalog in a fashion that is consumable by puppet agent, and > there does not seem to be a good way to ask puppetdb for a catalog which > can be applied that way either. > > > #puppet-dev suggestions of querying puppetdb for the most recent catalog > for $fqdn, and for running puppet catalog find $fqdn both don't seem to be > helpful, as the output doesn't appear to be consumable by puppet apply, and > as such, a graph can't be generated synthetically. > > the only way one could be generated afaik would be on a canary node. > > > If there is a way to generate a graph like this without actually applying > on a node, I'd love to hear it… additionally, if there's documentation on > doing this that I just simply missed, I'd love a pointer to it. > > > thanks a bunch. Much appreciated as always > > > -- > You received this message because you are subscribed to the Google Groups > "Puppet Developers" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/puppet-dev. > For more options, visit https://groups.google.com/groups/opt_out. > -- You received this message because you are subscribed to the Google Groups "Puppet Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/puppet-dev. For more options, visit https://groups.google.com/groups/opt_out.
