e breaking out all
> your logic into profile modules can be quite verbose and time-consuming.
> Sometimes you will get a profile class that does nothing but install a
> single package (e.g. if you have multiple profiles that require a single
> Apache module). That's OK. It will be MUCH
Hey List,
during the last weeks I finally managed to spend some quality time :) with
Puppet and I deepened my knowledge a bit: learned some ruby, wrote my first
custom ruby facts, used hiera in my latest module... it's been fun.
There is one concept with Hiera though which is still unclear for me
>
> $pp_shortcertname= "${trusted['certname']}".match(/([^.]+)\./)[1]
>
> not sure I fully understand why this works and [] doesn't.
>
> Not 100% sure I understand what the [1] does !
>
The parentheses are for capturing the matching text, and \1 for re-using it
as a backreference; [1] outside of t
7; },
> [possibly input4... inputN]
> }
> $input_merged = merge($input_base, $input_node)
> file { 'input_merged_file':
> content => template("template_that_uses_input_merged")
> }
>
> #Uses $port and $component params in individual File resources
> define inp
Dear List,
I've been using Puppet for over a year now and I'm quite enjoying it. I've
learned some stuff but there is of course always room for improvement. Now
I have a task which needs a nicer solution than I'm currently capable of.
I have a hash of items with to key/value pairs, which is *the
>
> So the ntp.conf should only contain the key identifiers pointing at the
> /etc/ntp.keys which won't be changed by Puppet.
>
Okay, it works exactly like this. I misinterpreted the description, one has
to specify the key identifiers - was misleading but probably it's just me.
So I can't edit t
