Vagrant: Is there Gemfile Equivalent for Vagrant Plugins?

[tknerr]

My Vagrantfiles start relying on more and more plugins, probably in a specific version each. How can I make sure that it loads the correct plugins in the correct version?

My first thought was that there must be something like a Gemfile equivalent for Vagrant plugins, but I couldn't find it in the docs. Is there?

[tknerr]

@mitchellh any pointers on this? Not supported right now? Plans for it? Or did I just miss how its done?

[fgrehm]

:+1: for this, I'm just not sure if it should be bundled with Vagrant itself or as a separate plugin

[tknerr]

@fgrehm nice idea, I guess it could be done via a plugin

[tknerr]

Here's a first stab at it, created with @damphyr during a ballmer peak at 4am:
https://github.com/tknerr/vagrant-plugin-bundler

[patcon]

_Really_ think this is needed. We're currently discussing how this feature is a concern for a project that's depending on vagrant.

[pirog]

agreed. have a pretty complex build that sometimes breaks when plugin versions change. would be great to specify.

[fgrehm]

Hey guys, here's my take on the problem: https://github.com/fgrehm/vundler :)

[patcon]

:heart:

[patcon]

Oh god, this is too perfect a name: _bindler_
I feel entirely way too smug right now.

http://dictionary.reference.com/browse/bindle
https://www.google.ca/search?q=bindle&tbm=isch

[mitchellh]

I think for now delegating this out to Vundler is ideal. Closing.

[shishirsharma]

Vundler is now deprecated we now again need this. @mitchellh can you suggest how to manage plugin requirements.

[hkdobrev]

:+1: For reopening this. There is no alternative at the moment.

[guilhem]

@mitchellh as many Vagrantfile options are specific to a plugin, and many time to a specific version of a plugin, it will be really good to being able to have something like "Gemfile" for Vagrant.

For the moment, to being able to share our project between developers, we have to put command lines in documentation...

[modius]

Vagrant 1.5+ offers Bundler support via a Gemfile: https://www.vagrantup.com/blog/vagrant-1-5-plugin-improvements.html#toc_1

[tknerr]

...but that's only used for plugin development, it will not help for
installing plugins into a "productive" vagrant environment :-/
Am 24.02.2015 06:09 schrieb "Geoff Bowers" [email protected]:

Vagrant 1.5+ offers Bundler support via a Gemfile:
https://www.vagrantup.com/blog/vagrant-1-5-plugin-improvements.html#toc_1

—
Reply to this email directly or view it on GitHub
https://github.com/mitchellh/vagrant/issues/1789#issuecomment-75700438.

[proteus-aholt]

looking for this exact support. currently, am working on creating a cohesive development environment solution for us, and am running into a plugin requirement that I would rather have automatically installed when "vagrant up" is called, rather than having it be an extra command.

looked at bindler, but it seems it is no longer supported.

I am echoing the above comment in that the gemfile support does not work for anything other than plugin development.

[cwc]

:+1:

[ut-adamc]

+1. Sometimes particular vagrantfiles need a gem and you really don't want to install it globally, even for Vagrant.

[tnguyen14]

Running into this question as well. +1 on opening this issue.

[darkn3rd]

Highly interested, this would make it simple to install plug-ins for the project. As a suggestion, there this could be part of the Vagrantfile, maybe have a plug-in preprocessor something like this:

plugin 'vagrant-aws', '>=0.7.0'
plugin 'vagrant-berkshelf', '>=4.0.3'

This would install such plug-ins if they did not exist already. There could also be a Pluginfile as well to install these outside of a vagrant up. You could then just do a vagrant plugin install without listing any particular plugin, and it will search $PWD for Pluginfile, and install the plugins from that file.