
Security News
New Website “Is It Really FOSS?” Tracks Transparency in Open Source Distribution Models
A new site reviews software projects to reveal if they’re truly FOSS, making complex licensing and distribution models easy to understand.
vagrant-plugin-bundler
Advanced tools
This is a Vagrant 1.2+ plugin which hooks in before vagrant up
and vagrant reload
and ensures that the required vagrant plugins as specified in your Vagrantfile are installed. Think of a minimalist Bundler for vagrant plugins.
Install using the standard Vagrant 1.1+ plugin installation method:
$ vagrant plugin install vagrant-plugin-bundler
After installing, you can specify the required plugin dependencies in your Vagrantfile
like so:
Vagrant.configure("2") do |config|
# require the vagrant-omnibus plugin...
config.plugin.depend 'vagrant-omnibus', '1.0.2'
# ...because we use it here:
config.omnibus.chef_version = "11.4.4"
...
end
Assuming the vagrant-omnibus plugin is not installed yet, vagrant up
will now fail:
$ vagrant up
Bringing machine 'foo' up with 'virtualbox' provider...
Version 1.0.2 of vagrant-omnibus required. No version found.
=> run `vagrant plugin install vagrant-omnibus --plugin-version 1.0.2` to fix this
Once you installed the missing plugin via vagrant plugin install
and thus the required plugin dependencies are met...
$ vagrant plugin install vagrant-omnibus --plugin-version 1.0.2
Installing the 'vagrant-omnibus --version '1.0.2'' plugin. This can take a few minutes...
Installed the plugin 'vagrant-omnibus (1.0.2)'!
...you can run vagrant up
again and it will continue as usual:
$ vagrant up
Bringing machine 'foo' up with 'virtualbox' provider...
[foo] Setting the name of the VM...
[foo] Clearing any previously set forwarded ports...
[foo] Fixed port collision for 22 => 2222. Now on port 2201.
[foo] Creating shared folders metadata...
[foo] Clearing any previously set network interfaces...
[foo] Preparing network interfaces based on configuration...
[foo] Forwarding ports...
[foo] -- 22 => 2201 (adapter 1)
[foo] Booting VM...
...
If you have multiple dependencies, you can specify them line by line:
# multiple plugin dependencies, one per line
config.plugin.depend 'vagrant-omnibus', '1.0.2'
config.plugin.depend 'vagrant-cachier', '0.1.0'
config.plugin.depend 'vagrant-aws', '0.2.2'
But it reads better if you use the block syntax:
# multiple plugin dependencies in a block
config.plugin.deps do
depend 'vagrant-omnibus', '1.0.2'
depend 'vagrant-cachier', '0.1.0'
depend 'vagrant-aws', '0.2.2'
end
git checkout -b my-new-feature
)git commit -am 'Add some feature'
)rake spec
)git push origin my-new-feature
)FAQs
Unknown package
We found that vagrant-plugin-bundler demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
A new site reviews software projects to reveal if they’re truly FOSS, making complex licensing and distribution models easy to understand.
Security News
Astral unveils pyx, a Python-native package registry in beta, designed to speed installs, enhance security, and integrate deeply with uv.
Security News
The Latio podcast explores how static and runtime reachability help teams prioritize exploitable vulnerabilities and streamline AppSec workflows.