wrightp

There is still work to be improved to get the word out. Docs have been updated: https://docs.chef.io/config_yml_kitchen.html Add option `install_strategy: always` and see if it behaves as you expect.

@mdunc In order to use the new attributes you must set `product_name`. Otherwise they will be ignored. This is currently using the previous default install method.

@mdunc No worries. These features are half-baked and only partial documented. We'll get back at it in the future.

Workaround: Once you run `get_contract` copy the contract address from `contract/_contract.json` and set that to CONTRACT_ADDRESS in the `config.js`. Then run the mint command.

applies to :size as well

There's a conflict here on the premise of allowing chef-provisioning to set sensible defaults, and the notion of failing the run when immutable attributes are changed via the resources. The...

@cheeseplus I had the day off but this idea came to me randomly. Could you try this updated version: https://gist.github.com/patrick-wright/7bf6e7345eb6d93fbeac

Alright. We've tried enough workarounds :) I tried one last thing to isolate the chef-client bootstrap from the machine run lists. The basic example in the description works. What this...

@schisamo I'll save you all the experimentation I conducted, but it looks like there's a conflict with the `package` resource's `:upgrade` action when used with the `source` property. I was...

If you are setting `package_source` it will always install the specified package. If you are relying on `channel` and `version`, mixlib-install will always install a later version if found. For...