Skip to content
A PowerShell module wrapper for the vagrant command line tool
PowerShell
Branch: master
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
docs
public
.gitignore
LICENSE
README.md
Vagrantey.psd1
Vagrantey.psm1
build.ps1

README.md

Vagrantey

Build Status

Working between multiple vagrant environements can really suck. You need to know their paths, and be in that directory to vagrant up the VagrantFile. This module streamlines that process by enabling you to configure all of your vagrant environments with a friendly name, and a path, which is stored in a json-formatted configuration file.

Starting up your various environments is then a simple Start-VagrantEnvironment -Environment $FriendlyName away. Similar functionality exists for destroying those environments.

The -Environment parameter is dynamically populated via an argumentcompleter which reads the configuration file to build the list of available options.

Installation

It should be enough to git clone https://github.com/steviecoaster/Vagrantey.git and load the psd1 file.

Example:

cd /users/svalding/Documents/Git
git clone https://github.com/steviecoaster/Vagrantey.git
ipmo ./Vagrantey/Vagrantey.psd1

From the Gallery:

Install-Module Vagrantey -Force

The following cmdlets are available:

  • Get-VagrantConfig
  • Set-VagrantConfig
  • Get-VagrantEnvironment
  • Start-VagrantEnvironment
  • Stop-VagrantEnvironment
  • Remove-VagrantEnvironment
  • Invoke-VagrantProvisioner
  • Get-VagrantPlugin
  • Remove-VagrantPlugin
  • Install-VagrantPlugin
  • Get-VagrantSnapshot
  • New-VagrantSnapshot
  • Remove-VagrantSnapshot
  • Restore-VagrantSnapshot
  • Get-VagrantBox
  • Remove-VagrantBox
  • Update-VagrantBox

Documentation

Documentation is in the docs folder, or available in shell via Get-Help $commandname.

You can’t perform that action at this time.