In puppet 3.2+ you can enable the future parser (--parser=future) which
allows iteration like that directly in the puppet language.
On 26 August 2013 03:58, Stefan Schmid sc...@web.de wrote:
Hi Mike
Yes, create_resources seems to be just right.
Thanks for the hint.
- Stefan
Am
Hi Mike
Yes, create_resources seems to be just right.
Thanks for the hint.
- Stefan
Am Sonntag, 25. August 2013 22:03:47 UTC+2 schrieb Mike Delaney:
Hi Stefan,
I believe for the general case, the best practice is to encapsulate the
logic that can't
be expressed directly in the PuppetDSL
Hi
I am new to puppet and need to manage host entries in file /etc/hosts as
follows on node mail.example.com and db.example.com. I do not want to
manage the whole file /etc/hosts with puppet, only a few entries.
puppet version 3.2.1
node mail.example.com, file /etc/hosts:
(..)
172.16.89.96
There's a host type built into puppet.
--
Brian Lalor
bla...@bravo5.org
On Aug 25, 2013, at 9:39 AM, Stefan Schmid sc...@web.de wrote:
Hi
I am new to puppet and need to manage host entries in file /etc/hosts as
follows on node mail.example.com and db.example.com. I do not want to manage
Hi Stefan,
I believe for the general case, the best practice is to encapsulate the
logic that can't
be expressed directly in the PuppetDSL in custom functions called from the
DSL.
Some of the features in the new experimental parser like iteration are
aimed at
reducing the need to write trivial,
