On Thursday, September 19, 2013 1:12:22 PM UTC-5, Jeremiah Jester wrote:
>
>
> class log_special
> (
> #log_special::log_vars: "test"
> $log_vars=log_vars,
>
>
Note that Puppet 3's automatic data binding will result in the value
associated with key 'log_special::log_vars' being bound to par
On Tuesday, September 24, 2013 11:07:59 PM UTC-5, mcd wrote:
>
> I'm confused at your snippets because they don't seem right. For instance,
> you show:
>
> #log_special::log_vars: "test"
> $log_vars=log_vars,
>
> But that doesn't look syntactically correct... I'm pretty sure that would
> fail t
I'm confused at your snippets because they don't seem right. For instance,
you show:
#log_special::log_vars: "test"
$log_vars=log_vars,
But that doesn't look syntactically correct... I'm pretty sure that would
fail to compile.
Anyway, I think if this really is what your yaml looks like:
log_spe
Chad,
Thanks for the reply. I am using /etc/puppet/heiradata for the
location of all my hiera files.
[root@puppet-master-t1 puppet]# ls hieradata/
defaults.yaml global.yaml groups hosts
Referencing non hashed/array variables from init.pp works. However, I
cannot get the array variable $log_st
I'm pretty sure we need more information than that.
1. Is puppet using the proper hiera.yaml? The command line client at
least used to use a different config than puppet (/etc/hiera.yaml vs
/etc/puppet/hiera.yaml). It sounds like you have this right, if you
are able to pull basic variables from
I've been able to retrieve data from hiera via init.pp from a basic
variable. However, when i try and pull an associative array from hiera, I'm
unable to get the data. I've verified that my yaml syntax is correct by
running hiera via the command line:
*hiera yaml file
log_special::log_vars:
