On Thu, May 12, 2011 at 3:06 AM, Felix Frank
<felix.fr...@alumni.tu-berlin.de> wrote:
> On 05/11/2011 01:50 AM, John Lyman wrote:
>> You can set "noop => true" in the package resource and puppet won't
>> actually change it, just log that it wants to change it.
>>
>> package { "httpd":
>> name => "httpd",
>> ensure => "latest",
>> noop => true,
>> }
>
> Yes, but this will still not install the package when its missing
> altogether.
I've had previous discussion about how to do this, and originally we
wanted to abuse facter to upload the package into inventory, but it's
not ideal for many reasons. You can use puppet inspect (2.6.5) to
audit the package version separately from your puppet run, or use
puppet resource package to get all package version on the system.
However you need upload the audit results and parse the results.
This is another crack at this issue, create a separate puppet
environment (I'm calling it checkpackage) with one difference in
site.pp, keep the rest of your manifests/modules the same:
Package <||> { ensure => latest, noop => true, tag => check }
On the client run against this new environment with tags check:
puppet agent -t --environment checkpackage --tags check
Here's a test manifests and you'll see the difference if you
comment/uncomment the first line:
Package <||> { ensure => latest, noop => true, tag => check }
class packages {
package { "yum":
ensure => present,
}
exec { "/bin/echo foo":
}
}
include packages
$ puppet apply --tags check test.pp
notice: /Stage[main]/Packages/Package[yum]/ensure: is
3.2.22-26.el5.centos, should be 3.2.22-33.el5.centos (noop)
Thanks,
Nan
--
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.
