Thanks Felix, for the heads up!
I was also thinking along the line that variables define() type variables
are not accessible from elsewhere.
w.r.t. inline_templates, what else would you suggest? The hiera hash that
I'm using here is something like this:
zpack_four::zpack_core:
> zenpack-apachemonitor:
> ver: latest
> repo: "zenoss-four-%{environment}"
> req: zenpack-apachemonitor
> zenpack-digmonitor:
> ver: latest
> repo: "zenoss-four-%{environment}"
> rqed: zenpack-apachemonitor
>
-San
On Thursday, June 5, 2014 12:47:32 PM UTC+1, Felix.Frank wrote:
>
> On 06/05/2014 01:06 PM, Sans wrote:
> > Later in my module, how can I use any of the variables (e.g. $zp_repo)
> > that are already defined in the zpack_installer?
>
> I strongly disbelieve that this can work.
>
> You can access variables defined in classes, but I would be mildly
> disturbed if there was a similar feature for accessing interna of
> defined type instances.
>
> If you have Hiera, you likely want to have your data in structured hiera
> values, so that you can look them up from all parts of your manifest.
>
> As an aside - inline_templates in defined types can be performance
> sinks, evaluating them is rather costly for the compiler.
>
> HTH,
> Felix
>
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/64f98cc6-0d80-43b7-9c88-c75285bcef28%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
