Re: [Puppet Users] Version recipes on a per-application level

2010-01-10 Thread Trevor Vaughan
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Does myapp have a module? If it does, I would suggest the following: node foo { $myapp_ver = '123' include "myapp" } - - /etc/puppet/modules/myapp/manifests/init.pp - class myapp { import "ver/*.pp" } - - /etc/puppet/modules/myapp/manifests/

Re: [Puppet Users] Version recipes on a per-application level

2010-01-10 Thread Pete Emerson
Okay, here's a proposed solution, what do you think? In site.pp: import "myapp/*/myapp.pp" In myapp/123/myapp.pp: if ($myapp_config == '123') { // recipes go here } In this way, all different myapp.pp files get imported, but only the rules inside the conditional for the desired version get

Re: [Puppet Users] Version recipes on a per-application level

2010-01-10 Thread Pete Emerson
I take it back, I can't have the site.pp dynamically generated via puppet, because potentially I need it to be different for each server. -- 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...@googlegrou

Re: [Puppet Users] Version recipes on a per-application level

2010-01-10 Thread Pete Emerson
As a followup (this is 0.25.1 by the way), I verified that what I was trying does not work: In site.pp if I do this: import "0.2/tester.pp" the rules in tester.pp execute, but if I try to use a puppet_node_classifier populated variable, it does not: import "$admin_config/tester.pp" No file(s) fo

Re: [Puppet Users] Version recipes on a per-application level

2010-01-10 Thread Pete Emerson
Hmm, I'm not sure this accomplishes what I'm looking for. I already have control over what versions get installed on which servers (via a puppet_node_classifier tied to a database). Let me go into a bit more detail. Maybe what you suggest applies, but I'm not seeing it quite yet. Thanks for your h

Re: [Puppet Users] Version recipes on a per-application level

2010-01-10 Thread R.I.Pienaar
hello, - "Trevor Vaughan" wrote: > -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

Re: [Puppet Users] Version recipes on a per-application level

2010-01-10 Thread Trevor Vaughan
-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. Tre

[Puppet Users] Version recipes on a per-application level

2010-01-10 Thread Pete Emerson
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 applicat