Re: [Puppet Users] Augeas JSON example?

t it with the other lenses, and on the "list of core lenses" page it's there but the link goes to a page which doesn't exist. I think it's amazing that I was able to cobble together what I already have, and I think once I get this all figured out, I'll have to

[Puppet Users] Augeas JSON example?

ot;keys" within the file. Is anybody doing something similar, and if so, would you mind sharing the relevant bits of your manifests? Or point me to an example of a WORKING augeas resource which adds or -- John Simpson Unix System/VM Developer and Engineering Operations, Voalte +1 (941) 312-2830 x

[Puppet Users] puppet master --compile: extra output?

onds Is there a way to tell it NOT to generate this line? Google is telling me nothing useful, and I have trouble believing I'm the first person to notice this. -- John Simpson Unix System/VM Developer and Engineering Operations, Voalte -- You received this message because you are subs

[Puppet Users] modulepath ordering question

making the environments totally separate and having to full copy of one environment in order to use my test environment (although if that's the only way to do it, I'm not totally against doing it.) -- John Simpson Unix System/VM Developer and Engineering Operations, Voalte +1 (941) 312-

Re: [Puppet Users] Noob question about the ${name} variable

tiated at the time. The real problem I was trying to solve is that I didn't want to have to type each filename twice, primarily because it opens up a potential source of errors if the names aren't typed exactly the same. Creating a "wrapper" around the file object allows the

Re: [Puppet Users] Noob question about the ${name} variable

On 2013-09-25, at 0819, Brian Lalor wrote: On Sep 25, 2013, at 8:12 AM, John Simpson wrote: > >> file { '/etc/httpd/conf.d/ssl.conf' : >> ensure => file , >> content => template ( "${module_name}{$name}.erb" ) , >> } >> >> H

[Puppet Users] Noob question about the ${name} variable

/httpd/conf.d/ssl.conf.erb". Why does $name expand differently in these cases, and where did I miss this in the documentation? -- John Simpson Unix System/VM Developer and Engineering Operations, Voalte +1 (941) 312-2830 x148 -- You received this message because you are subscribed to the G

Re: [Puppet Users] ignoring a service that doesn't exist

I've done the following, it ended up being a bit simpler for me when I'm not sure what random services a new CentOS install has installed and/or enabled... define no_service ( ) { service { "${name}" : ensure => stopped , enable => false , status => "stat -t /etc/rc?.d/S?