I would avoid this approach - global variables aren't a good idea. Hiera would be a better approach:
http://www.devco.net/archives/2011/06/05/hiera_a_pluggable_hierarchical_data_store.php http://www.devco.net/archives/2011/06/06/puppet_backend_for_hiera.php -Eric -- Eric Shamow Professional Services http://puppetlabs.com/ (c)631.871.6441 On Saturday, February 11, 2012 at 7:08 PM, krish wrote: > > My scenario is this: I have 4 environments, Dev, Test, QA, Prod. Each > > of these environments lives in 2 sites, LA and NY. I have 5 > > applications that are site and env specific. > > > > I want to use puppet to template-ize the config files that is required > > for each env, per site, per app, so 40 files. > > > > The config file is basically key=value pairs. Here's a simple example > > of what each file may look like: > > > > site=LA > > env=Dev > > app=App1 > > masterServer=host1 > > clientServer1=host2 > > clientServer2=host3 > > > > > > How about having these key value pairs in site.pp with a case environment > Then they become global to all modules. > > > > -- > Krish > olindata.com (http://olindata.com) > > -- > 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 > (mailto:puppet-users@googlegroups.com). > To unsubscribe from this group, send email to > puppet-users+unsubscr...@googlegroups.com > (mailto:puppet-users+unsubscr...@googlegroups.com). > For more options, visit this group at > http://groups.google.com/group/puppet-users?hl=en. > > -- 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.
