[chef] Re: Re: Re: Re: Re: Re: Re: Re: Re: delayed evaluation?


Chronological Thread 
  • From: John Alberts < >
  • To:
  • Subject: [chef] Re: Re: Re: Re: Re: Re: Re: Re: Re: delayed evaluation?
  • Date: Wed, 18 Dec 2013 16:48:46 -0800

Thanks again to everyone for their input.  I think it's been decided beyond a shadow of a doubt that I should implement this in a custom provider. :)

A question to Ranjib's example; where can I find more information about node.run_state?  I only see mention of it regarding a windows provider and really no where else.



On Wed, Dec 18, 2013 at 4:40 PM, Sean OMeara < " target="_blank"> > wrote:
You want to implement this as an atomic operation from within a custom provider.


On Wed, Dec 18, 2013 at 7:10 PM, John Alberts < " target="_blank"> > wrote:

On Wed, Dec 18, 2013 at 10:17 AM, Dan Razzell < " target="_blank"> > wrote:
Isn't the issue only that %x[ls /tmp] is being evaluated at compile time?  Avoid that notation and you'll be able to do what you intend.  Use "system" instead and it will be evaluated as part of the ruby block.

I thought any ruby code inside a ruby block will not be evaluated during compile time and instead during the normal order of the execution phase.  I haven't tested this yet, but does it really matter if inside that ruby block I've used, %x[ls /tmp] or `ls /tmp` or system("ls /tmp") ?



--
John Alberts




--
John Alberts



Archive powered by MHonArc 2.6.16.

§