Puppet users - Apr 2009 - Concatenating properties files

I''m new to puppet, and I''m hoping to use it to configure our
production apps, each of which is configured from a single Java
properties file.

So we have a lot of redundant properties in these files, and I''d like
to consolidate them using puppet.  For example, I''d like to "roll
up"
these properties into separate files based on logical "tiers",
e.g. service, data center, or host.

So, for example, I might have service Foo running on host Bar in data
center Baz.  I''m envisioning three properties files:
foo.properties, bar.properties, and baz.properties.  But what I need
puppet to push is a single file, app.properties, which is a
concatenation of the three.

I haven''t figured out an elegant way of doing this.  I thought I might
be able to set the sourceselect attribute of the file type to
''all''
but that only works with recursive copies.  :-(

Another option is to use templates, since multiple ones will be
concatenated together, but this seems kind of goofy since I won''t
actually be replacing any tokens in the templates.  Plus, there won''t
always be a properties file for each tier, e.g. there may not be a
bar.properties file if the target host doesn''t need to override any
property set by the service.

So I''m kind of at a loss and hoping for some guidance...

Thanks,
Jim

--~--~---------~--~----~------------~-------~--~----~
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+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en
-~----------~----~----~----~------~----~------~--~---

On 2009-Apr-7, at 2:55 PM, Jim Crossley wrote:
> So, for example, I might have service Foo running on host Bar in data
> center Baz.  I''m envisioning three properties files:
> foo.properties, bar.properties, and baz.properties.  But what I need
> puppet to push is a single file, app.properties, which is a
> concatenation of the three.
There is probably a better way, but…

I think you could accomplish this using variable substitution in the  
file''s "content". So, you might have something like:

     $foo = "# foo stuff
     # more stuff"

     $bar = "# bar stuff"

     $baz = "# baz stuff"

     file { "app.properties":
       content => "$foo
     $bar
     $baz
     ",
     }

And then you could have some logic that sets $foo, $bar, and $baz to  
the right values prior to defining the file resource. (Mind your  
indentation and newlines when using "content".)

-- 
Rob McBroom
<http://www.skurfer.com/>

Because it screws up the order in which people normally read text.

Original message:
> Why is it bad to top-post your reply?

--~--~---------~--~----~------------~-------~--~----~
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+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en
-~----------~----~----~----~------~----~------~--~---