On 2016-04-02 11:46, Martin Alfke wrote:
On 01 Feb 2016, at 19:15, Henrik Lindberg
wrote:
That is exactly what you should do. An external (file based epp) when called,
does not get to see variables in the scope from which it was called/used. This
design is
On 2016-02-02 21:15, John Bollinger wrote:
On Monday, February 1, 2016 at 12:15:12 PM UTC-6, henrik lindberg wrote:
Contrast this with the inline_epp, which you can think of as a
lambda/code-block. Here the code block gets to see the variables in
scope, since it is itself in that
On 2016-04-02 14:40, Martin Alfke wrote:
On 04 Feb 2016, at 14:30, Henrik Lindberg
wrote:
On 2016-04-02 11:46, Martin Alfke wrote:
This especially feels bad, when we will have performance improvement for epp in
the future.
I have not seen tickets with
On Monday, February 1, 2016 at 12:15:12 PM UTC-6, henrik lindberg wrote:
Contrast this with the inline_epp, which you can think of as a
> lambda/code-block. Here the code block gets to see the variables in
> scope, since it is itself in that scope (part of the same piece of code).
>
>
Hmmm.
On 2016-01-02 24:23, Martin Alfke wrote:
Hi,
I recently had an issue with epp template within a defined resource type.
Let’s assume the following code snippets:
# modules/test/manifests/init.pp
class test {
::test::files { 'test':
param1 => 'value',
}
}
#