Because this ticket was not in "resolved" status, it was not noticed when we did code review for the COOK project, but COOK-1179 was, and I merged that. Sorry I missed this!
Having a mercurial SCM provider is good, any way you slice it. Ideally, such a provider would subclass Chef's built in SCM resource so it can be used similar to the subversion and git resources (as well as in other places like the deploy resource).
Thoughts on improving this library to do that? Noah Kantrowitz also did done some work on this kind of provider.
May have fixed this in the
COOK-879branch of this clone:https://github.com/zombiedev/cookbooks/tree/COOK-879
I haven't tested this yet as I'm on Windows machine right now and I don't think the SCM resources and providers will work well with chef-solo on windows. Will try post a chef-client run showing this works sometime in the next few days.