You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 10, 2023. It is now read-only.
I think mysql2_chef_gem cookbook was just split out of the database cookbook, but that should be a pretty quick fix. Would be great to get to working with newer database cookbooks, as right now the very strict cookbook requirement is making berkshelf dependency resolution unhappy
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Since we didn't lock
database
cookbook,database
cookbook version now is 4.0.1.From 2.3.1 to 3.0.0 (chef-boneyard/database@v2.3.1...v3.0.0#diff-9fd042d4cd1e8f82894bbd7dffb313ecL19), it changed the dependency of the cookbook.
Somehow running
vagrant provision centos6
in development it will throw error oncould not find recipe mysql for cookbook database
The fix is to lock the
database
version like thisdepends 'database', '~> 2.3.1'
I will send a pull request soon.
related to #59
The text was updated successfully, but these errors were encountered: