Hi Felix,
I think I have this sorted now with the log level stuff that denmat
suggested.
Basically it was a typo in my test but my point was I could not get to see the
catalogue that my test was testing against.
Puppet file:
concat::fragment{'foo':
path=> '/etc/foo',
content => 'set
That seems to be it. Thanks. I thought I had tried that yesterday but it
gave no more output.
john
On Wednesday, 7 May 2014 23:21:06 UTC+1, denmat wrote:
>
> Hi,
>
> You need to include the puppet logging in you rspec file.
>
> I can't remember what that is off the top of my head but I'm pretty s
Hi,
can you share a sample manifest and spec test that expose this problem?
I do not yet clearly understand what you're trying to do.
Thanks,
Felix
On 05/07/2014 04:42 PM, choffee wrote:
> Am I doing this wrong?
>
> I create a test that says "check for a file named foo", write some code
> that
Hi,
You need to include the puppet logging in you rspec file.
I can't remember what that is off the top of my head but I'm pretty sure this
will help you along the way.
http://www.ruempler.eu/2012/04/03/puppet-rspec-debugging/?mobile=1
> On 8 May 2014, at 0:42, choffee wrote:
>
> Am I doin
Am I doing this wrong?
I create a test that says "check for a file named foo", write some code
that should create the file. It fails for whatever reason and the test just
says no.
How do I get a clue what I am doing wrong? It seems obvious to me that
having the catalog that was tested against
