It works, thanks.
Benoit Decherf wrote:
> Create a definition that create the environments :
>
> define prepare_env() {
>
> $env = $name
>
> file { "e${env}-website1":
> ...
> }
> ...
>
> }
>
>
> And in a class, call it with the array "envs":
>
> class main_class {
>
>
I'm struggling to figure out how to do this as I just don't know what
to search for...
What we have: e1 - e9 (e1 being dev, e9 being prod, middle
environments being test machines of various degrees).
All environments have a fixed set of websites, call them eX-website1,
eX-website2, etc...
On so
Luke Kanies wrote:
> The only way to do it is to set the logdest for puppetmasterd on
> startup, but I believe that has been broken in some versions because
> it's used so rarely.
Ok after a lot of playing I finally found out that not all options
that work at the cli work in the config, logdest i
On May 12, 3:41 pm, James Turnbull wrote:
> Have a look at
> thehttp://reductivelabs.com/trac/puppet/wiki/ConfigurationReferencepage
> and the various log options.
I've looked there.
I've got sensible values set for all of the log related config.
The closest I could find to an answer was:
mas
Is it possible to completely disable logging to syslog and only log to
a file?
--~--~-~--~~~---~--~~
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
T
> josb has provided a 1.9 compatibility patch, but we stupidly have not
> merged it in yet.
>
> It'll be in 0.25, though.
Where can we find this patch?
Or alternatively is 0.25 coming out fairly soon?
--~--~-~--~~~---~--~~
You received this message because you ar