[chef] Re: chef_handler LWRP resources are always listed as updated

[Noah Kantrowitz < >]

On May 28, 2013, at 4:45 PM, Morgan Blackthorne wrote:

> This seems to be a result of this ticket: 
> http://tickets.opscode.com/browse/COOK-620
> 
> My gut feeling is that there should be a good way to check and see whether 
> or not it needs to be reloaded, if it already has been loaded, rather than 
> just reloading and reenabling it on every run. I'm not sure exactly what 
> the best way to do that would be.
> 
> For a single file, including a version or a checksum in the filename for 
> the handler that gets written to /var/cache/handlers/ would be pretty 
> straightforward; if the version or checksum is different it will need to 
> load the new handler (although this would mean that we would have to be 
> very careful about the logic to determine what old handler to unload, if 
> previously active). However, I'm not sure if people are tying handlers into 
> gems, and if they are it's entirely possible that the changes might not be 
> in the file that is being pushed out, and thus undetected when the reload 
> is necessary.
> 
> I'm not sure if my quest for "0 resources updated" as the result of 
> back-to-back runs is worthwhile or not, but it's one of the things I've 
> been working on of late. :)

The chef_handler LWRP actually does reload on every run, so this is correct. 
There is otherwise not enough information about the state of the client 
unfortunately, and we can't really mtime/checksum a code object safely :-/

--Noah

Attachment: signature.asc
Description: Message signed with OpenPGP using GPGMail