This sounds super similar to the Debian Linux case, where `apt-get update` needs to be run before the package manager will list new versions of packages.
With Debian, it was decided (long before I joined the company) that Puppet shouldn't do that operation on every run - both because it can be slow to talk to another server, what to do if it fails is hard to judge, and also because admins may want to control how and when their local package database is synchronized with external servers.
The apt module provides an `apt::update` class that can be used to cause package system to be synchronized as part of a catalog application, either on a schedule or every time puppet runs. I think a similar module/class is probably called for in the Solaris world.
-- Branan
--
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 puppet-dev+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-dev/b4173f95-02ee-46fe-a25f-8fc4c8b11717%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.