Hi,
as I've answered on SF, I'd recommend [R.I.Pienaar's concat][1] module.
With this you can export/collect configuration file snippets and
concatenate them on the target into a single file.
Best Regards, David
[1]: http://github.com/ripienaar/puppet-concat
--
dasz.at OG Tel: +43 (0)664 2602670 Web: http://dasz.at
Klosterneuburg UID: ATU64260999
FB-Nr.: FN 309285 g FB-Gericht: LG Korneuburg
> That module helped me implement one of the proposed solutions. I though
> there might be something "prettier" to handle this kind of situations,
> but seems not.
Nope. That is the "best practice" mechanism for doing this. Sorry.
Daniel
--
✣ Daniel Pittman ✉ dan...@rimspace.net ☎ +61 401 155 707
♽ made with 100 percent post-consumer electrons
Not quite. Best practice would be to implement a native type which
parses out the config file, but that involves ruby.
Best Regards, David
I do this with templates with embedded ruby. This is not the best
practice, it's pretty far away from it.
Your solution with exported resources is almost the same, except the
fact you're using file (when I'm using a database)
The only problem I see is when you have multiple upstream : how will you
know in which upstream you want a server to be ?
Regarding the concat module I don't see how to use it for this because
some "calculations" have to be made.
To me the only "quick" solution is a template embedding ruby, and the
only "clean" solution is a native type (longer to do/test/maintain) as
David suggests.
My 2c
Nico.