-
-
Notifications
You must be signed in to change notification settings - Fork 91
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Get rid of chef_gem. #21
Conversation
chef_gem fails because build-essential isn't installed at compile time. The Chef guys are recommending that complex things like replicaset and mongos become LWRPs, which is probably in progress but this fixes the chef_gem issue quickly.
Not sure if this is the best idea… it works as a quick fix I'd address the issue with compile time with Check: https://github.com/chef-brigade/mongodb-cookbook/pull/14/files |
LGTM so long as it gets a comment explaining when we can rip it out |
@@ -24,7 +24,15 @@ | |||
node.override['mongodb']['instance_name'] = 'mongos' | |||
|
|||
include_recipe 'mongodb::install' | |||
include_recipe 'mongodb::mongo_gem' | |||
|
|||
ruby_block 'chef_gem_at_converge_time' do· |
This comment was marked as outdated.
This comment was marked as outdated.
Sorry, something went wrong.
This comment was marked as outdated.
This comment was marked as outdated.
Sorry, something went wrong.
This comment was marked as outdated.
This comment was marked as outdated.
Sorry, something went wrong.
Closing in favor of #39 |
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Source: edelight/chef-mongodb#370