You are going to probably need something along the lines of
context => '/files/etc/hosts.allow'
changes => [
'ins 01 after *[last()]',
'set 01/process[1] ssh',
'set 01/process[2] ssh2',
'set 01/client ipaddr'
]
onlyif => 'match *[process[1] == 'ssh' and 'client' == 'ipaddr'] size == 0'
yo
spec/classes/test__c_spec.rb
This doesn't
rspec spec/classes/test__c_spec.rb spec/classes/test_spec.rb
Running them both separately works too.
On Monday, October 29, 2012 2:48:25 PM UTC-5, Nathan Huff wrote:
>
> Looks like the subnamespace thing isn't important either. Just
Looks like the subnamespace thing isn't important either. Just having two
classes triggers this as well.
On Monday, October 29, 2012 1:13:05 PM UTC-5, Nathan Huff wrote:
>
> OK so I have what I think is a minimal test case here:
>
> https://github.com/nhuff/spec-failure
>
27;. With both spec files in place the
system complains about anchor not being defined.
If you remove the test file for test::c the test for class test will pass.
On Monday, October 29, 2012 10:36:50 AM UTC-5, Nathan Huff wrote:
>
> A super simple module that just has a file and anchor res
> -Jeff
>
> On Fri, Oct 26, 2012 at 8:01 AM, Nathan Huff
> >
> wrote:
> > I am trying to figure out if I am missing something simple here. After
> > upgrading to puppet 3.0 running puppet-rspec tests that use
> > custom resources from modules in the fixtur
I am trying to figure out if I am missing something simple here. After
upgrading to puppet 3.0 running puppet-rspec tests that use
custom resources from modules in the fixtures directory are failing. I
have a module that uses the anchor type and with 2.7.19 it works fine.
After upgrading to 3.
