)]}'
{"Rakefile":[{"author":{"_account_id":7128,"name":"Mark Vanderwiel","email":"vanderwl@us.ibm.com","username":"kramvan"},"change_message_id":"8c51c2c8bf27d9b3f2863c5be7ac36efc832609f","unresolved":false,"context_lines":[{"line_number":39,"context_line":""},{"line_number":40,"context_line":"desc \"All-in-One build\""},{"line_number":41,"context_line":"task :allinone \u003d\u003e :create_key do"},{"line_number":42,"context_line":"  run_command(\"chef-client #{client_opts} -o \u0027provisioning::vagrant_linux,provisioning::allinone\u0027\")"},{"line_number":43,"context_line":"end"},{"line_number":44,"context_line":""},{"line_number":45,"context_line":"desc \"Multi-Node build\""}],"source_content_type":"application/octet-stream","patch_set":2,"id":"3aaa91ec_51c82b74","line":42,"updated":"2016-06-24 18:39:02.000000000","message":"Humm, does this force all jobs down the new provisioning path?   I guess I was expecting to see all the all recipes and related files deleted with this patch to give us just one way  to do this, not two.\n\nOr, do we need both paths for a while?  In that case, please update main ReadMe to reflect how this repo is used and laid out.","commit_id":"876e98a662dc44d4e1c37e3d511b109c9cb10201"},{"author":{"_account_id":14790,"name":"Samuel Cassiba","email":"samuel@cassi.ba","username":"scassiba"},"change_message_id":"dcbc4dbf253ae2bf71ceb176e12735a19356e8d5","unresolved":false,"context_lines":[{"line_number":39,"context_line":""},{"line_number":40,"context_line":"desc \"All-in-One build\""},{"line_number":41,"context_line":"task :allinone \u003d\u003e :create_key do"},{"line_number":42,"context_line":"  run_command(\"chef-client #{client_opts} -o \u0027provisioning::vagrant_linux,provisioning::allinone\u0027\")"},{"line_number":43,"context_line":"end"},{"line_number":44,"context_line":""},{"line_number":45,"context_line":"desc \"Multi-Node build\""}],"source_content_type":"application/octet-stream","patch_set":2,"id":"3aaa91ec_512f8ba0","line":42,"in_reply_to":"3aaa91ec_51c82b74","updated":"2016-06-24 19:06:41.000000000","message":"This does force all jobs down the path of using the new provisioning cookbook. For continued use of chef-client in local mode, in order to chain recipes together like we have been doing, it has to be in a cookbook. The cookbook is only to be used within the context of launching the VM upon which to converge. I\u0027ll update the main README to describe its function.\n\nInitially, just to get things working so we can relax the hard requirement on 0.9.0, I forklifted the provisioning recipes into a cookbook. I have verified locally that this format works with chefdk 0.9.0 all the way through to 0.15.15 when executing the allinone / multi_node tasks.","commit_id":"876e98a662dc44d4e1c37e3d511b109c9cb10201"}],"site-cookbooks/provisioning/README.md":[{"author":{"_account_id":7128,"name":"Mark Vanderwiel","email":"vanderwl@us.ibm.com","username":"kramvan"},"change_message_id":"8c51c2c8bf27d9b3f2863c5be7ac36efc832609f","unresolved":false,"context_lines":[{"line_number":2,"context_line":""},{"line_number":3,"context_line":"This cookbook is used for serving chef-provisioning recipes for provisioning"},{"line_number":4,"context_line":"OpenStack with Chef. It is intended to be referenced by chef-client in"},{"line_number":5,"context_line":"local-mode a la ChefDK."},{"line_number":6,"context_line":""},{"line_number":7,"context_line":"# recipes"},{"line_number":8,"context_line":""}],"source_content_type":"text/x-gfm","patch_set":2,"id":"3aaa91ec_b1f50fee","line":5,"updated":"2016-06-24 18:39:02.000000000","message":"Since this is for a newer level of ChefDK, maybe record the min version here?","commit_id":"876e98a662dc44d4e1c37e3d511b109c9cb10201"}]}
