I keep running into the following upgrade pattern.

Previous Puppet run declared:
file { "my_jar.1.2.3.jar": ... }

New puppet run declares:
file {"my_jar.2.4.6.jar": ... }

But the new puppet run doesn't delete the older versions of this jar file.

Is there a standard puppet pattern for removing older versions of jars
without explicitly naming each version?

The overall pattern is...

declare resource file { "my_jar.1.2.3.jar": }
ensure absent for all older versions of my_jar
ensure => "1.2.3" (imaginary code since version is specified in the
only restart service if my_jar.nnn.jar has changed

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+unsubscribe@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Search Discussions

Related Discussions

Discussion Navigation
viewthread | post
Discussion Overview
grouppuppet-users @
postedApr 24, '13 at 9:24p
activeApr 24, '13 at 9:24p

1 user in discussion

Larry Fast: 1 post



site design / logo © 2022 Grokbase