- From: Nate Mueller <
- Subject: [[chef-dev]] remote_file checksum behavior
- Date: Tue, 8 Sep 2009 10:57:36 -0700
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:date:x-google-sender-auth:message-id:subject :from:to:content-type; b=WCmm+/4O931C2s7pcJ0ZMUDJz8LbTnv1TcJ7V9r0fY8CjAlKykf97a4UZ4tnCIHF2a E3l2ESpMUo+uy/waKWiD0zgPnChV15VkXBE+l6btmWwhkfiJIABy48Ou8n8biBL4GbMn jMfhpnf7Gmy8mKCMsakPhJaafGNyjlh4kXJWE=
I'm working on a chef deployment and noticed that anything that subscribed to or was notified by a remote_file resource would still run if the file was unchanged. It looks like do_remote_file does an initial comparison between the declared checksum for the new file and the actual checksum for the old file. If you don't specify a checksum or the checksums mismatch it fetches the file, computes a checksum and uses that going forward. If the real checksums match it won't create a backup file but it will still copy the new file over and set @updated.
Is that the desired behavior? Seemed strange to me so I patched it locally but I'm new around here so I wanted to check before filing it.
- [[chef-dev]] remote_file checksum behavior, Nate Mueller, 09/08/2009
Archive powered by MHonArc 2.6.16.