-
Notifications
You must be signed in to change notification settings - Fork 4.4k
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
Need a way to run custom Ohai plugins #908
Comments
There are two ways of doing that:
The second option will give user more flexibility. |
Either works for me. Though I suspect that @mitchellh will prefer the first option, since it's similar to how cookbook and role paths are already specified. |
Here is the option №2 https://github.com/mhorbul/vagrant/tree/custom_template |
Definitely interested in this. Was going to hack something similar. That being said, I had pulled the fork, but didn't succeed at building it as a local gem. I'll admit I haven't done a lot of gem creation before. Had a bit of a failure bundle install |
have you tried "bundle exec rake" ? |
I think for now #1 is the way to go for sure. But in the future I think arbitrary Chef config templates should be supported. |
No dice for me (unless I need to go to 1.9) /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/bin/ruby -S rspec test/unit/vagrant/action/builder_test.rb test/unit/vagrant/action/environment_test.rb test/unit/vagrant/action/runner_test.rb test/unit/vagrant/action/warden_test.rb test/unit/vagrant/box_collection_test.rb test/unit/vagrant/box_test.rb test/unit/vagrant/command/base_test.rb test/unit/vagrant/config/base_test.rb test/unit/vagrant/config/loader_test.rb test/unit/vagrant/config/v1/root_test.rb test/unit/vagrant/config/v1_test.rb test/unit/vagrant/config_test.rb test/unit/vagrant/data_store_test.rb test/unit/vagrant/downloaders/base_test.rb test/unit/vagrant/downloaders/file_test.rb test/unit/vagrant/downloaders/http_test.rb test/unit/vagrant/environment_test.rb test/unit/vagrant/hosts_test.rb test/unit/vagrant/plugin/v1_test.rb test/unit/vagrant/registry_test.rb test/unit/vagrant/util/ansi_escape_code_remover_test.rb test/unit/vagrant/util/file_checksum_test.rb test/unit/vagrant/util/hash_with_indifferent_access_test.rb test/unit/vagrant/util/is_port_open_test.rb test/unit/vagrant/util/line_endings_helper_test.rb test/unit/vagrant/util/network_ip_test.rb test/unit/vagrant/util/retryable_test.rb test/unit/vagrant_test.rb version: On branch custom_templatenothing to commit (working directory clean) |
Although I may have gotten around this by using the vagrant-ohai plugin from here: |
bundle exec rake install worked fine at least when I pulled directly from the mitchellh repo and tried on 1.0.3 |
Was this ever solved? |
For what it's worth, it looks like Opscode's ohai cookbook takes care of this somehow. |
I recently commited 56adfec which will be part of the next Vagrant release (1.2.4 or 1.3.0) that allows custom configuration to be set for Chef, allowing you to do this sort of thing. |
As far as I can tell, there is no way to specify the plugin path for Ohai. This means custom Ohai plugins cannot be loaded by the Chef provisioner.
See: http://wiki.opscode.com/display/chef/Loading+Custom+Ohai+Plugins
The text was updated successfully, but these errors were encountered: