[Puppet Users] Accessing variable from a user defined resource in the same module

That's a warning, not an error. Code that elicits such warnings works in
Puppet 2.7 the same way it worked in Puppet 2.6. Nevertheless, you should
fix the problem, and the message tells you how to do so.



Again, that's a warning, not an error. If $vip_addr_gw is a local variable
in the context from which the template is evaluated, a parameter of the
class or definition that invokes template() or inline_template(), then it's
also bogus.



Class vs. defined type does not make a difference for issues of that kind.



You can't, but you don't need to do it that way. At all.

1. Each class and definition should be in its own file
2. An object whose nature precludes being applied more than once should
be a class, not a definition
3. Any class's variables (except class parameters in some versions of
Puppet) can be accessed from anywhere in the manifest set by their
fully-qualified names (i.e. $module::class::variable)

That leaves you at least two options. If you convert the singleton
definitions to classes, then you can access their variables via their
fully-qualified names. If you want to leave them as definitions then you
can store the needed values as variables of some class (as I think you said
you did), and then read those class variables where you need them instead
of trying to access the parameter values of the defined-type instance.


It shouldn't. The big picture, in case it was not apparent in the
foregoing, is to pull the authoritative source of the needed values out of
the definition to some place accessible to everyone who wants it. Common
choices for such a place include variables of some class and external data
(perhaps accessed via hiera).


John