----- Original Message -----
> On 01/06/2012 02:40 PM, R.I.Pienaar wrote:
> > The only sane way imho is to diff the catalogs.
>
> Maybe, but a different (not necessarily claiming "sane") choice is to
> 1. run puppetmaster 2.8 on a non-standard port
> 2. have each agent perform a --noop run using this masterport
> 3. collect reports from the agents, see if they would erase your SSH
> keys etc.
>
> That's basically what I like to do whenever upgrading my master.
yes, you'd then also need to do a detailed audit of the reports to make
sure that no resources are suddenly unmanaged - imagine:
if $foo {
# manage package bar
}
the behavior of that simple if changed between major versions of puppet
some time ago and the report based approach wouldnt pick that up unless
you very carefully audit and compare every reported resource.
When I wrote the differ the puppet reports didnt have the level of detail
required to do the audit purely on reports they do now, so if you were going
between 2 versions of puppet that supported the detailed reporting this would
indeed be a better approach.
Still though - relationships can change, be missing etc and those owuldnt
be in reports either.
It's basically just extremely complex and I dont think there's a truly right
answer but there should be one if the 2.7.x series is anything to go by thanks
to the ever changing landscape of features and behaviors
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@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.
