Im going to second this guy. I believe puppet should ALWAYS collect facts after it is done. The amount of changes it can make to a server, during a catalog run, can be massive. Without reporting those changes, bad things can occur. It really really limits the potential of having a complete and correct inventory system.
As Paul has done, I too make the last thing to run on all my catalogs, another upload of puppet facts. Now I know what changes have been made. There are many other people out there that have requested this, so we can't be the only ones. On a most basic level, I dont see any possible way to argue for the current method. Current method: Collect facts -> change system config -> Don't collect those changes Our method: Collect facts -> change system config -> recollect change facts -- 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/1578d17c-783a-49ff-94e1-1be1577f6a60%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
