kitchen-vagrant | A Test Kitchen Driver for Vagrant
kandi X-RAY | kitchen-vagrant Summary
kandi X-RAY | kitchen-vagrant Summary
A Test Kitchen Driver for Vagrant. This driver works by generating a single Vagrantfile for each instance in a sandboxed directory. Since the Vagrantfile is written out on disk, Vagrant needs absolutely no knowledge of Test Kitchen. So no Vagrant plugins are required. A Vagrant version of 1.1.0 or higher is required for this driver which means that a native package must be installed on the system running Test Kitchen. If you are creating Windows VMs over a WinRM Transport, then the vagrant-winrm Vagrant plugin must be installed. As a consequence, the minimum version of Vagrant required is 1.6 or higher. If you would like to use VMware Fusion or Workstation you must purchase the software from VMware and also purchase the corresponding Vagrant VMware Plugin.
Support
Quality
Security
License
Reuse
Top functions reviewed by kandi - BETA
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of kitchen-vagrant
kitchen-vagrant Key Features
kitchen-vagrant Examples and Code Snippets
Community Discussions
Trending Discussions on kitchen-vagrant
QUESTION
When I try to run kitchen test
on terminal I'm greeted with
ANSWER
Answered 2020-Feb-11 at 18:21I faced the same error when I ran 'kitchen create' in ~/chef-repo/cookbooks/mycookbook
directory.
I resolved it by running the following command in my macOS Terminal window.
QUESTION
I have had a number of issues recently with vagrant-berkshelf
not syncing Chef cookbooks on an existing machine reliably. And, basically, when doing research on workarounds, I see something like:
vagrant-berkshelf is deprecated, use Test Kitchen instead.
My use case is that I have Vagrantfile
s, used to build VMs and DigitalOcean droplets, that are hand-written and only use Chef to provision the VMs. I am most definitely approaching Chef as a user, not an author or tester of cookbooks.
So, I am in a case of Vagrant -> Chef
, not Chef -> Vagrant
.
When looking at Kitche-Vagrant, I see that:
The kitchen-vagrant driver for Kitchen generates a single Vagrantfile for each instance of Kitchen in a sandboxed directory..
My question is: if my workflow relies on hand-written, complex, Vagrantfiles, can I continue to use Chef as a provisioner without having to rely on vagrant-berkshelf
?
Some of the possible alternatives I see are:
mangle Test Kitchen configuration to work with my exiting Vagrantfile. I fear that this is not the intent of this tool and will not end well.
use
chef.cookbooks_path
attribute in vagrant and let it take the place of vagrant-berkshelf.switch out provisioners and use say Vagrant->Ansible.
The Vagrantfile below is somewhat simplified, but the gist is that the Vagrantfile is in charge and Chef is just used to provision.
...ANSWER
Answered 2018-Feb-28 at 21:45It isn't deprecated per se, but it does no longer have a maintainer and does highly recommend against its use. There is no replacement for the workflow you describe. Sorry. If you are interested in taking over as maintainer, I can put you in contact with the team.
QUESTION
I'm trying to learn Ansible with Vagrant (Ubuntu/trusty64) and I'm trying to use test-kitchen to assert my setup.
The problem I am having is the Vagrant machine has an old version of Ruby (1.9.1) and therefore one of the dependencies (busser) fails to run. The error I am receiving is:
...ANSWER
Answered 2018-Jan-04 at 21:30Thanks to Hubert above, I changed
this
QUESTION
I need some lights about two concepts: roles
and environments
. I know what they stand for, nevertheless I don't quite figure out:
- Where should I set them up? On my workstation and then I need to upload them? Or I've to define them on my chef server?
- I've several recipes inside my
recipes
folder. Where should I define roles?
EDIT
Currently, I'm using this folder structure:
...ANSWER
Answered 2017-May-24 at 12:26Roles and environments are stored in the roles
and environments
directories respectively.
All code and json data on your infrastructure should be stored in a chef-repo. If you installed chef-dk (the Chef Development Kit) on your workstation - which I highly suggest - you can generate such a chef-repo using the chef generate repo
command. The structure of such a repo looks like this, and you should follow it even when not using chef generate
(README
files are optional :) ):
QUESTION
With the following software versions installed: Berkshelf - 2.0.18 Ruby - 2.2.2 Vagrant - 1.9.3 test-kitchen - 1.15.0 kitchen-vagrant - 1.1.0 Chef Server API version - 11.0.2
I am attempting to run test kitchen on my local system. In doing so, I have a berksfile that points to a chef_api :config with a single recipe apt
...ANSWER
Answered 2017-Apr-13 at 23:44Berkshelf 2.0 is very old, the current version is 5.x. We only support Berkshelf installed via ChefDK so please remove all existing copies and then install via the normal ChefDK installers.
Community Discussions, Code Snippets contain sources that include Stack Exchange Network
Vulnerabilities
No vulnerabilities reported
Install kitchen-vagrant
On a UNIX-like operating system, using your system’s package manager is easiest. However, the packaged Ruby version may not be the newest one. There is also an installer for Windows. Managers help you to switch between multiple Ruby versions on your system. Installers can be used to install a specific or multiple Ruby versions. Please refer ruby-lang.org for more information.
Support
Reuse Trending Solutions
Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items
Find more librariesStay Updated
Subscribe to our newsletter for trending solutions and developer bootcamps
Share this Page