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


Chronological Thread 
  • From: Sean OMeara < >
  • To:
  • Subject: [chef] Re: Re: Re: Re: Re: Re: Re: Re: delayed evaluation?
  • Date: Wed, 18 Dec 2013 19:40:32 -0500

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




Archive powered by MHonArc 2.6.16.

§