>Henrik Lindberg writes:
>> On 03/10/16 15:48, jcbollinger wrote:
>> The behavior you describe seems buggy to me, but your manifests are also
>> unusual. Specifically, it is strange for test/manifests/init.pp to
>> contain a top-scope declaration. It is especially strange for that
>> declaration
On 03/10/16 15:48, jcbollinger wrote:
On Friday, September 30, 2016 at 2:03:06 PM UTC-5, Toni Schmidbauer wrote:
Henrik Lindberg > writes:
> On 28/09/16 14:30, Toni Schmidbauer wrote:
> I tried this on latest puppet:
>
> === test.pp
> class test::subclass {}
> clas
On Friday, September 30, 2016 at 2:03:06 PM UTC-5, Toni Schmidbauer wrote:
>
> Henrik Lindberg > writes:
>
> > On 28/09/16 14:30, Toni Schmidbauer wrote:
> > I tried this on latest puppet:
> >
> > === test.pp
> > class test::subclass {}
> > class test inherits test::subclass {
> > notify
Henrik Lindberg writes:
> On 28/09/16 14:30, Toni Schmidbauer wrote:
> I tried this on latest puppet:
>
> === test.pp
> class test::subclass {}
> class test inherits test::subclass {
> notify { 'hello?': }
> }
> include test
did some more tests with puppet 4.7. so the above works but if i move
On 28/09/16 14:30, Toni Schmidbauer wrote:
hi,
it's a stupid example but nevertheless it would be interesting to now
why the following throws a duplicate resource error under puppet 3.7.4
and puppet 4.2.1
test/manifests/init.pp:
# start puppet code
class test inherits test::subclass {
notify
hi,
it's a stupid example but nevertheless it would be interesting to now
why the following throws a duplicate resource error under puppet 3.7.4
and puppet 4.2.1
test/manifests/init.pp:
# start puppet code
class test inherits test::subclass {
notify { 'hello?': }
}
include test
#end puppet cod
