Plugin Development: Packaging & Distribution
This page documents how to organize the file structure of your plugin and distribute it so that it is installable using standard installation methods. Prior to reading this, you should be familiar with the plugin development basics.
Warning: Advanced Topic! Developing plugins is an advanced topic that only experienced Vagrant users who are reasonably comfortable with Ruby should approach.
The best way to describe packaging and distribution is to look at how another plugin does it. The best example plugin available for this is vagrant-aws.
By using Bundler and Rake, building a new
vagrant-aws package is easy. By simply calling
rake package, a
gem file is dropped into the directory. By calling
the gem is built and it is uploaded to the central RubyGems
repository so that it can be installed using
vagrant plugin install.
Your plugin can and should be this easy, too, since you basically get this for free by using Bundler.
To setup your project, run
bundle gem vagrant-my-plugin. This will create a
vagrant-my-plugin directory that has the initial layout to be a RubyGem.
You should modify the
vagrant-my-plugin.gemspec file to add any
dependencies and change any metadata. View the vagrant-aws.gemspec
for a good example.
Do not depend on Vagrant for your gem. Vagrant is no longer distributed as a gem, and you can assume that it will always be available when your plugin is installed.
Once the directory structure for a RubyGem is setup, you will want to modify your Gemfile. Here is the basic structure of a Gemfile for Vagrant plugin development:
source "https://rubygems.org" group :development do gem "vagrant", git: "https://github.com/hashicorp/vagrant.git" end group :plugins do gem "my-vagrant-plugin", path: "." end
This Gemfile gets "vagrant" for development. This allows you to
bundle exec vagrant to run Vagrant with your plugin already loaded,
so that you can test it manually that way.
The only thing about this Gemfile that may stand out as odd is the
"plugins" group and putting your plugin in that group. Because
vagrant plugin commands do not work in development, this is how
you "install" your plugin into Vagrant. Vagrant will automatically
load any gems listed in the "plugins" group. Note that this also
allows you to add multiple plugins to Vagrant for development, if
your plugin works with another plugin.
Next, create a
Rakefile that has at the very least, the following
require "rubygems" require "bundler/setup" Bundler::GemHelper.install_tasks
If you run
rake -T now, which lists all the available rake tasks,
you should see that you have the
release tasks. You
can now develop your plugin and build it!
You can view the vagrant-aws Rakefile for a more comprehensive example that includes testing.
To manually test your plugin during development, use
bundle exec vagrant to execute Vagrant with your plugin loaded
(thanks to the Gemfile setup we did earlier).
For automated testing, the vagrant-spec project provides helpers for both unit and acceptance testing plugins. See the giant README for that project for a detailed description of how to integrate vagrant-spec into your project. Vagrant itself (and all of its core plugins) use vagrant-spec for automated testing.