Weirdo error about 'undefined method checksum' during symlink about artifact-cookbook

[jwalton]

What's especially weird is, when I try this on a vagrant VM, it works fine. Grrr...

[jwalton]

By way of workaround, I commented out:

# symlinks ({
#     ".migrate-migrating" => "migrations/.migrate-migrating",
#     "local_config.coffee" => "configs/local_config.coffee"
# })

And added to the end of my before_symlink proc:

   script "do_symlink" do
       interpreter "bash"
       user "root"
       code <<-EOH
            ln -s "#{shared_dir}/.migrate-migrating" "#{release_path}/migrations/.migrate-migrating"
            ln -s "#{shared_dir}/local_config.coffee" "#{release_path}/configs/local_config.coffee"
        EOH
    end

Which, of course, fixes it.

[KAllan357]

Hi, thanks for the report! I have a few random thoughts that I'll place here:

Just to make sure, do all of your link resources work in your before_symlink proc?

I noticed this line in your gist - https://gist.github.com/jwalton/da1634758061e190f049#file-partial-output-L39 - if your before_symlink is creating that file, there could be something bad happening when Chef attempts to make that directory.

Every time I come back to the symlinks code, I get slightly confused. I believe the intent is to symlink folders into the deploy directory and create them under shared.

Either way, the symlinks attribute is confusing and should be improved upon. Please let me know if any of my (somewhat random) thoughts help!

[jwalton]

I don't have any link resources in before_symlink, as I was relying on symlinks. :P

The readme says "symlinks - A hash that maps files in the shared directory to their paths in the current release", which makes it sound like it should work for plain files as well as for directories (and, like I said, it works on a vagrant VM for inexplicable reasons). I agree; the symlink code is a bit strange - I wonder if the intent is just to make sure that the file or directory being linked to is owned by the correct user with sane permissions, and create it if it doesn't exist? Perhaps some logic is required to check and see if the target is a file or a directory? I can try writing this up and seeing if it fixes the problem...

I still don't understand what any of this has to do with checksum, though. :(