New Chef-provisioning version has broken Chef-Provisioning-oneview

[thebsdbox]

Hello,

Trying to fix a bug I created a new environment with the latest release of Chef, a gem dependency in the one view driver means that the driver now gives an error on run.

    Gem::ConflictError
    ------------------
    Unable to activate chef-provisioning-oneview-1.2.0, because chef-provisioning-2.0.2 conflicts with chef-provisioning (~> 1.0)

I've quickly edited the local .gemspec to change from ~> 1.0 to >= 0 and it's working with the 2.x release of the chef-provisioning driver. But the remote gem will need modifying.

-Dan

[jsmartt]

Definitely need to add/confirm support for chef-provisioning 2.0. I don't want to just say it's compatible without doing some modifications and checking into what broke or was changed in 2.0 though.

[jsmartt]

Btw, it doesn't look like a lot changed, other than the version of Ruby required and the version of Cheffish (see this). I think the biggest impact this has on us is limiting which versions of the chef-client that are compatible. From the looks of things, it looks like anything older than chef 12.14 won't be supported.

[thebsdbox]

Sure, just took me by surprise that I guess the hard limit broke all of the pulling of the required gems.