Skip to content

Available Vagrant Plugins

Emiliano Ticci edited this page Apr 9, 2016 · 170 revisions

Disclaimer

Before Vagrant 1.4.2 there are two distinct names for each one of the plugins that you need to know:

  • rubygem name (used for installing plugin, via $ vagrant plugin install rubygem-plugin-name)
  • internal name (used in Vagrantfile, via Vagrant.has_plugin?('Internal_Plugin_Name') )

With Vagrant 1.4.2 and later you just need to know the rubygem name of the plugin that will work either for $ vagrant plugin install and for Vagrant.has_plugin?().

The following list has both names in this order: rubygem name /internal name/

Chef

Puppet

Local Domain Resolution

/etc/resolver approach

/etc/hosts approach

Registrar approach

  • vagrant-dns-updater -- A Vagrant plugin that allows you to automatically configure a subdomain with the ip of your vagrant instance using your registrar API. Only the registrar OVH is supported for the moment.

Route53

  • vagrant-aws-dns -- A Vagrant plugin that allows you to set up route53 records for instances created using vagrant-aws provider.

Guests

Providers

Provisioners

Shared Folders

Host Interaction

Testing / BDD

Networking

Snapshots

  • sahara -- snapshot support (integrated into Vagrant 1.8+)
  • vagrant-multiprovider-snap -- snapshotting for Virtualbox and VMWare through the same interface (integrated into Vagrant 1.8+)

Uncategorized

Other (related)

  • vagrant-status Powershell prompt modification that shows the basic status of Vagrant machines in the current directory
  • oh-my-vagrant An easy to manipulate development environment for using vagrant with puppet, docker and more!
  • vagrant-web. Web application (written in php) to manage machines (nodes), virtual machines, boxes, configurations, etc. It is required that each machine runs vagrant-node.

Obsolete / Deprecated

Something went wrong with that request. Please try again.