Vagrant - a must have to integrate with Chef
February 12, 2021

Vagrant - a must have to integrate with Chef

Anonymous | TrustRadius Reviewer
Score 9 out of 10
Vetted Review
Verified User

Overall Satisfaction with Vagrant

In my organization, Vagrant is used to managing VMs using VirtualBox and Chef Client as the provisioner. This allows users to automatically install software, change configurations and all of the lifecycle used to deploy later on production, without any additional concerns during the process of development, since is a VM-controlled environment.
  • Contained development environments on VMs, but with same structure as production environments
  • Open-source
  • Huge community
  • Easy to set up
  • It was great if Vagrant consumes less resources than what consumes today
  • Vagrant had a very positive impact, since it was really easy to set up on our organisation, without any cost
Fast[er] to implement than Docker. Even consuming a lot of resources, consume less resources than Docker. Cheaper than Azure, since [it] is free.

Do you think HashiCorp Vagrant delivers good value for the price?


Are you happy with HashiCorp Vagrant's feature set?


Did HashiCorp Vagrant live up to sales and marketing promises?

I wasn't involved with the selection/purchase process

Did implementation of HashiCorp Vagrant go as expected?


Would you buy HashiCorp Vagrant again?


Vagrant is well suited to be integrated with Chef, in order to execute configured code on one or more platforms in isolation. Associating Vagrant as a tool for building and managing virtual machine environments in a single workflow, we get an entire group of tools that are a must-have when an organization has lots of platforms that can share some configuration.