Skip to content
A Vagrant plugin that ensures the desired version of Chef is installed via the platform-specific Omnibus packages.
Branch: master
Clone or download
Latest commit 0345dd5 Jan 3, 2019
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
lib Bump chefstyle and fix warnings Jun 5, 2018
locales Adding error for Vagrant version mismatch Sep 2, 2014
test use a more durable Ubuntu LTS in Linode tests Dec 17, 2018
.gitignore Initial commit! Created during first Opscode Hackathon! Apr 2, 2013
.rspec Convert specs to rspec 3 format Aug 26, 2016
.travis.yml Try modern vagrant Jun 5, 2018
.yardopts Initial commit! Created during first Opscode Hackathon! Apr 2, 2013
CHANGELOG.md Add github_changelog_generator and release 1.5.0 Aug 31, 2016
Gemfile Use latest vagrant-linode version Jun 14, 2018
LICENSE
README.md Add deprecation warning Jan 3, 2019
Rakefile
vagrant-omnibus.gemspec

README.md

vagrant-omnibus

Deprecation Warning

This is no longer an actively maintained Chef project. We believe that Test Kitchen offers a far superior development and testing experience as it allows fine grained control of versions, better platform support, and and overall better experience. If this project works for you that's great, but we'd highly suggest using https://kitchen.ci/ instead.


Gem Version Build Status Code Climate

A Vagrant plugin that ensures the desired version of Chef is installed via the platform-specific Omnibus packages. This proves very useful when using Vagrant with provisioner-less baseboxes OR cloud images.

The plugin should work correctly with most all providers that hook into Vagrant::Action::Builtin::Provision for provisioning and is known to work with the following Vagrant providers:

Installation

Ensure you have downloaded and installed Vagrant 1.1 or newer from the Vagrant downloads page. If you require Windows support then Vagrant 1.6.1 or newer is needed.

Installation is performed in the prescribed manner for Vagrant 1.1 plugins.

$ vagrant plugin install vagrant-omnibus

Usage

The Omnibus Vagrant plugin automatically hooks into the Vagrant provisioning middleware. You specify the version of the Chef Omnibus package you want installed using the omnibus.chef_version config key. The version string should be a valid Chef release version or :latest.

Install the latest version of Chef:

Vagrant.configure("2") do |config|

  config.omnibus.chef_version = :latest

  ...

end

Install a specific version of Chef:

Vagrant.configure("2") do |config|

  config.omnibus.chef_version = "14.2.0"

  ...

end

Specify a custom install script:

Vagrant.configure("2") do |config|

  config.omnibus.install_url = 'http://acme.com/install.sh'
  # config.omnibus.install_url = 'http://acme.com/install.msi'
  # config.omnibus.install_url = '/some/path/on/the/host'

  ...

end

If vagrant-cachier is present and config.cache.auto_detect enabled the downloaded omnibus packages will be cached by vagrant-cachier. In case you want to turn caching off:

Vagrant.configure("2") do |config|

  config.omnibus.cache_packages = false

  ...

end

This plugin is also multi-vm aware so it would possible to say install a different version of Chef on each VM:

Vagrant.configure("2") do |config|

  config.vm.define :new_chef do |new_chef_config|

    ...

    new_chef_config.omnibus.chef_version = :latest

    ...

  end

  config.vm.define :old_chef do |old_chef_config|

    ...

    old_chef_config.omnibus.chef_version = "13.9.1"

    ...

  end
end

Tests

Unit

The unit tests can be run with:

rake test:unit

The test are also executed by Travis CI every time code is pushed to GitHub.

Acceptance

Currently this repo ships with a set of basic acceptance tests that will:

  • Provision a Vagrant instance.
  • Attempt to install Chef using this plugin.
  • Perform a very basic chef-solo run to ensure Chef is in fact installed.

The acceptance tests can be run against a subset of the Vagrant providers listed above. The acceptance tests can be run with:

rake test:acceptance:PROVIDER_NAME

And as expected, all acceptance tests only uses provisioner-less baseboxes and cloud images!

Contributing

  1. Fork it
  2. Create your feature branch (git checkout -b my-new-feature)
  3. Commit your changes (git commit -am 'Add some feature')
  4. Push to the branch (git push origin my-new-feature)
  5. Create new Pull Request

Authors

Seth Chisamore (schisamo@chef.io)

You can’t perform that action at this time.