On Tue, Jan 20, 2015 at 9:40 AM, jcbollinger wrote:
> There seems to be a bit of a terminology gap here. Class['a'] does not
> "have" a service.pp in any useful sense of the term. I suppose you probably
> mean that module 'a' has a class or defined type "a::service" whose
> definition resides in
On Friday, January 16, 2015 at 12:48:19 PM UTC-6, Weeve wrote:
>
> On Thu, Jan 15, 2015 at 9:53 AM, jcbollinger > wrote:
> >
> > In any case, if $foo does not resolve to a class or resource reference,
> then
> > why does catalog building succeed? (Or perhaps the problem actually
> > manife
On Thu, Jan 15, 2015 at 9:53 AM, jcbollinger wrote:
>
> In any case, if $foo does not resolve to a class or resource reference, then
> why does catalog building succeed? (Or perhaps the problem actually
> manifests as catalog building failure)
Feels like I've been staring at the problem too
On 2015-15-01 15:53, jcbollinger wrote:
On Wednesday, January 14, 2015 at 8:08:25 PM UTC-6, Felix.Frank wrote:
On 01/14/2015 03:47 PM, Jason Wever wrote:
> Hi All,
>
> I having a problem in where I'm defining a File Type and setting the
> requires parameter to use a var
On Wednesday, January 14, 2015 at 8:08:25 PM UTC-6, Felix.Frank wrote:
>
> On 01/14/2015 03:47 PM, Jason Wever wrote:
> > Hi All,
> >
> > I having a problem in where I'm defining a File Type and setting the
> > requires parameter to use a variable name (e.g. requires => $foo).
> > However, w
On 01/14/2015 03:47 PM, Jason Wever wrote:
> Hi All,
>
> I having a problem in where I'm defining a File Type and setting the
> requires parameter to use a variable name (e.g. requires => $foo).
> However, when I do this, the Puppet run doesn't act like it's
> translating the variable into what it
Hi All,
I having a problem in where I'm defining a File Type and setting the
requires parameter to use a variable name (e.g. requires => $foo).
However, when I do this, the Puppet run doesn't act like it's
translating the variable into what it should be set to. $foo should
resolve to either Class
