Nan, that's exactly what I thought. I posted another thread with more
details on the issue I'm seeing though, so I won't go into my issues here.
On Friday, July 15, 2011 1:42:23 PM UTC-4, Nan Liu wrote:
>
> Facts are top scope, so simply ::factname such as
> scope.lookupvar('::operatingsystem')
>
Facts are top scope, so simply ::factname such as
scope.lookupvar('::operatingsystem')
On Fri, Jul 15, 2011 at 8:26 AM, Greg Etling wrote:
> Justin,
> What would the syntax be along those lines when looking up custom facts?
>
> --
> You received this message because you are subscribed to the Goog
Justin,
What would the syntax be along those lines when looking up custom facts?
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/puppet-users/-/BB3TAoW6PVEJ.
To post to t
I've been using:
scope.lookupvar('puppet::params::certdnsnames')
On Thu, Jul 14, 2011 at 8:45 PM, lurdan wrote:
> hi,
>
> What's the best way to refer variables which pass as defined resource
> parameter
> from template erbs?
>
> I've been made many modules which has resource definitions contai
hi,
What's the best way to refer variables which pass as defined resource
parameter
from template erbs?
I've been made many modules which has resource definitions containing
file templating.
After I upgrade my puppet version to 2.7.0rc (debian experimental),
I'm getting many
warnings "Dynamic loo
