Just to make sure I fully understand this subject, could some provide a
little meta-example of what node variables and dynamic scoping are? I'm
sure I'm not the only one unsure here :)
On Thu, Dec 22, 2011 at 16:07, jcbollinger john.bollin...@stjude.orgwrote:
On Dec 21, 3:07 pm, zoredache
On Wed, 2011-11-16 at 06:54 -0800, jcbollinger wrote:
Starting in Puppet 2.8, however, it will be mandatory to refer to non-
local variables by their fully-qualified names. In preparation for
that, Puppet 2.7.x emits warning when your manifests resolve non-local
variables from the dynamic
On 11/16/11 3:54 PM, jcbollinger wrote:
On Nov 16, 3:59 am, flexfrostyn...@gmail.com wrote:
I read the guide
athttp://docs.puppetlabs.com/guides/scope_and_puppet.htmlandothers'
mail, i am a little confused now, below is my understanding:
1. top scope only refers to site.pp, not include
Very thanks for your detailed explanation :)
For the last question, what doubt me is only fact variables in a template
which is invoked by a define will throw the warning,
if the template is invoked by a class, everything is ok.
On Wed, Nov 16, 2011 at 10:54 PM, jcbollinger
Does the @ method is supported by puppet 2.8? During my test, it can also
be used not only ahead facts variable but also the variable in its parent
class, it is this a wordaround for dynamic scope problem?
On Thu, Nov 17, 2011 at 2:39 AM, Nigel Kersten ni...@puppetlabs.com wrote:
On Wed, Nov
