-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 When I've needed to do this, I let the Package type handle version upgrades and then wrote a custom fact to detect the version that was installed and adjust the system accordingly.
You could also use node-specific variables or defines to do this. Trevor On 01/10/2010 02:32 PM, Pete Emerson wrote: > A while ago I got some help from here about how to version my puppet > recipes. The solution was to generate an /etc/puppet.conf file via > puppet to create environments like this: > > [v01] > manifest = /etc/puppet/manifests/v01/site.pp > > Now, I want to move control of the puppet recipes to the application > level. > > In my puppet_node_classifier, I have some variables that define an > application's version (which puppet uses to 'upgrade' an application > from one version to the next): > > puppet_node_classifier node > --- > parameters: > myapp_version: "123" > > Now, what I would like to be able to do is take that variable and use > it to include puppet recipes. Something along the lines of this in my > site.pp, which doesn't work: > > import "myapp/$myapp_version/myapp.pp" > > Can anyone point me in the right direction as to how I might do this > sort of versioning of my puppet recipes? > > Thanks, > Pete > - -- Trevor Vaughan Vice President, Onyx Point, Inc. email: tvaug...@onyxpoint.com phone: 410-541-ONYX (6699) - -- This account not approved for unencrypted sensitive information -- -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAktKSCYACgkQyWMIJmxwHpRt6wCeOMds18e4DBylLSIYaueOINT1 g3sAn3uXIC+mgnHyWXV4Uz7pg7PXorfV =FN90 -----END PGP SIGNATURE-----
-- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@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.
