batali-wedge 0.0.4 → 0.1.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: fe25ce84ec427ce5890f795a124c82641ff81dd8
-  data.tar.gz: 675f2514c87139dfe9ec33fc8d925bf2b4c0ab76
+  metadata.gz: e6f124231d53d1814403f5400386e24a8545241d
+  data.tar.gz: 62d952e59accd7f3f5e1612a599f1a68ed11ddc2
 SHA512:
-  metadata.gz: 458287805264a5d83887e0240b2a14c821bb85638178730fcfda82a95c0859539d444ae0acd4440804b45e76ea4efec185163394c513c08a085d4d159e85ef9a
-  data.tar.gz: f8ea5fb97d6d05fddf685d41efaff62b9c8f1038639cc3f56fd7522c77bc35e95216a89a1c6207e5e04303cf6004193297daa2a563d4fb0da6ce08503f76fdfc
+  metadata.gz: 9d29e1eb3dfd9b83bdb99c2c20dd577ae15602c9fad0bec2451e9d2ce54157b049cb871de5a155ea5ee553bf4c6ed6bb67b5ce5575ee44d187096f655e517512
+  data.tar.gz: b136b66efd8da4256ed80410cad2c7f1d76ba97cb99db12481b8c86345098d1e4fe00e4745f9182d23ca882c7c31a22c0f66cee0621d386454c7910e7e2547e9

data/CHANGELOG.md

@@ -0,0 +1,2 @@
+# v0.1.0
+* Initial release

data/README.md

@@ -0,0 +1,50 @@
+# Batali Wedge
+
+Lets have some fun with `chef-client`!
+
+## Wedge Batali
+
+This gem wedges Batali into `chef-client` to perform cookbook
+resolution locally on the node, and request the solution set
+from the Chef Server.
+
+## OMG WHY!?
+
+There were old complaints about local solvers not generating
+the same results as the solver on the server. So, what if we
+just used the same solver, then you'd know you had the same
+resolution. This lead to:
+
+> I wonder if Batali could be wedged into the client
+
+As it turns out, it can.
+
+## Usage
+
+This only support 12.2.x versions of Chef. The gem needs to be
+installed into the omnibus like so:
+
+```
+$ /opt/chef/emebedded/bin/gem install batali-wedge --no-document
+```
+
+Then you can enable it via the `client.rb` file by adding this to
+the top:
+
+```ruby
+# /etc/chef/client.rb
+
+require 'batali-wedge/sync'
+```
+
+## What does this provide?
+
+Cookbook resolution, just on the client, via Batali. There's no
+least impact yet, but mostly because this was a first pass to
+see _if_ it would work. The next release will likely include
+that feature just to see what happens.
+
+# Info
+
+* Repository: https://github.com/hw-labs/batali-wedge
+* IRC: Freenode @ #heavywater

data/lib/batali-wedge/sync.rb

@@ -60,6 +60,8 @@ class Chef::PolicyBuilder::ExpandNodeObject
     results = solver.generate!
     solution = results.pop
     solution_output = solution.units.sort_by(&:name).map{|u| "#{u.name}<#{u.version}>"}.join(', ')
+    node.set[:batali] ||= Mash.new
+    node.set[:batali][:last_resolution] = Mash[solution.map{|u| [u.name, u.version]}]
     Chef::Log.warn "Batali cookbook resolution: #{solution_output}"
     Hash[
       solution.units.map do |unit|

data/lib/batali-wedge/version.rb

@@ -1,3 +1,3 @@
 module BataliWedge
-  VERSION = Gem::Version.new('0.0.4')
+  VERSION = Gem::Version.new('0.1.0')
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: batali-wedge
 version: !ruby/object:Gem::Version
-  version: 0.0.4
+  version: 0.1.0
 platform: ruby
 authors:
 - Chris Roberts