Downloads:

264,513

Downloads of v 1.3.5:

864

Last Update:

16 Oct 2013

Package Maintainer(s):

Software Author(s):

  • Mitchell Hashimoto
  • John Bender

Tags:

vagrant virtual machine VM VirtualBox VMware

Vagrant

This is not the latest version of Vagrant available.

1.3.5 | Updated: 16 Oct 2013

Downloads:

264,513

Downloads of v 1.3.5:

864

Software Author(s):

  • Mitchell Hashimoto
  • John Bender

Vagrant 1.3.5

This is not the latest version of Vagrant available.

All Checks are Unknown

2 Test of Unknown Status


Validation Testing Unknown


Verification Testing Unknown

To install Vagrant, run the following command from the command line or from PowerShell:

>

To upgrade Vagrant, run the following command from the command line or from PowerShell:

>

To uninstall Vagrant, run the following command from the command line or from PowerShell:

>

NOTE: This applies to both open source and commercial editions of Chocolatey.

1. Ensure you are set for organizational deployment

Please see the organizational deployment guide

  • Open Source or Commercial:
    • Proxy Repository - Create a proxy nuget repository on Nexus, Artifactory Pro, or a proxy Chocolatey repository on ProGet. Point your upstream to https://chocolatey.org/api/v2. Packages cache on first access automatically. Make sure your choco clients are using your proxy repository as a source and NOT the default community repository. See source command for more information.
    • You can also just download the package and push it to a repository Download

3. Enter your internal repository url

(this should look similar to https://chocolatey.org/api/v2)

4. Choose your deployment method:


choco upgrade vagrant -y --source="'STEP 3 URL'" [other options]

See options you can pass to upgrade.

See best practices for scripting.

Add this to a PowerShell script or use a Batch script with tools and in places where you are calling directly to Chocolatey. If you are integrating, keep in mind enhanced exit codes.

If you do use a PowerShell script, use the following to ensure bad exit codes are shown as failures:


choco upgrade vagrant -y --source="'STEP 3 URL'"
$exitCode = $LASTEXITCODE

Write-Verbose "Exit code was $exitCode"
$validExitCodes = @(0, 1605, 1614, 1641, 3010)
if ($validExitCodes -contains $exitCode) {
  Exit 0
}

Exit $exitCode

- name: Ensure vagrant installed
  win_chocolatey:
    name: vagrant
    state: present
    version: 1.3.5
    source: STEP 3 URL

See docs at https://docs.ansible.com/ansible/latest/modules/win_chocolatey_module.html.

Coming early 2020! Central Managment Reporting available now! More information...


chocolatey_package 'vagrant' do
  action    :install
  version  '1.3.5'
  source   'STEP 3 URL'
end

See docs at https://docs.chef.io/resource_chocolatey_package.html.


Chocolatey::Ensure-Package
(
    Name: vagrant,
    Version: 1.3.5,
    Source: STEP 3 URL
);

Requires Otter Chocolatey Extension. See docs at https://inedo.com/den/otter/chocolatey.


cChocoPackageInstaller vagrant
{
   Name     = 'vagrant'
   Ensure   = 'Present'
   Version  = '1.3.5'
   Source   = 'STEP 3 URL'
}

Requires cChoco DSC Resource. See docs at https://github.com/chocolatey/cChoco.


package { 'vagrant':
  provider => 'chocolatey',
  ensure   => '1.3.5',
  source   => 'STEP 3 URL',
}

Requires Puppet Chocolatey Provider module. See docs at https://forge.puppet.com/puppetlabs/chocolatey.


salt '*' chocolatey.install vagrant version="1.3.5" source="STEP 3 URL"

See docs at https://docs.saltstack.com/en/latest/ref/modules/all/salt.modules.chocolatey.html.

5. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

This package was approved as a trusted package on 13 Jul 2015.

Description

Vagrant is a tool for building complete development environments using virtual machines. With an easy-to-use workflow and focus on automation, Vagrant lowers development environment setup time, increases development/production parity, and makes the "works on my machine" excuse a relic of the past.


Log in or click on link to see number of positives.

In cases where actual malware is found, the packages are subject to removal. Software sometimes has false positives. Moderators do not necessarily validate the safety of the underlying software, only that a package retrieves software from the official distribution point and/or validate embedded software against official distribution point (where distribution rights allow redistribution).

Chocolatey Pro provides runtime protection from possible malware.

Version Downloads Last Updated Status
Vagrant (Install) 2.2.8 1317 Tuesday, May 5, 2020 Approved
Vagrant (Install) 2.2.7 11927 Thursday, January 30, 2020 Approved
Vagrant (Install) 2.2.6 11814 Tuesday, October 15, 2019 Approved
Vagrant (Install) 2.2.5 13062 Wednesday, June 26, 2019 Approved
Vagrant (Install) 2.2.4 13169 Thursday, February 28, 2019 Approved
Vagrant (Install) 2.2.3 7131 Thursday, January 10, 2019 Approved
Vagrant (Install) 2.2.2 5704 Wednesday, November 28, 2018 Approved
Vagrant (Install) 2.2.1 2473 Friday, November 16, 2018 Approved
Vagrant (Install) 2.2.0 5103 Wednesday, October 17, 2018 Approved

This package has no dependencies.

Discussion for the Vagrant Package

Ground Rules:

  • This discussion is only about Vagrant and the Vagrant package. If you have feedback for Chocolatey, please contact the Google Group.
  • This discussion will carry over multiple versions. If you have a comment about a particular version, please note that in your comments.
  • The maintainers of this Chocolatey Package will be notified about new comments that are posted to this Disqus thread, however, it is NOT a guarantee that you will get a response. If you do not hear back from the maintainers after posting a message below, please follow up by using the link on the left side of this page or follow this link to contact maintainers. If you still hear nothing back, please follow the package triage process.
  • Tell us what you love about the package or Vagrant, or tell us what needs improvement.
  • Share your experiences with the package, or extra configuration or gotchas that you've found.
  • If you use a url, the comment will be flagged for moderation until you've been whitelisted. Disqus moderated comments are approved on a weekly schedule if not sooner. It could take between 1-5 days for your comment to show up.
comments powered by Disqus