kitchen-vagrant | A Test Kitchen Driver for Vagrant

 by   test-kitchen Ruby Version: v1.14.1 License: Non-SPDX

kandi X-RAY | kitchen-vagrant Summary

kandi X-RAY | kitchen-vagrant Summary

kitchen-vagrant is a Ruby library. kitchen-vagrant has no bugs, it has no vulnerabilities and it has low support. However kitchen-vagrant has a Non-SPDX License. You can download it from GitHub.

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

            kandi-support Support

              kitchen-vagrant has a low active ecosystem.
              It has 346 star(s) with 191 fork(s). There are 31 watchers for this library.
              OutlinedDot
              It had no major release in the last 12 months.
              There are 18 open issues and 170 have been closed. On average issues are closed in 274 days. There are 1 open pull requests and 0 closed requests.
              It has a neutral sentiment in the developer community.
              The latest version of kitchen-vagrant is v1.14.1

            kandi-Quality Quality

              kitchen-vagrant has 0 bugs and 0 code smells.

            kandi-Security Security

              kitchen-vagrant has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.
              kitchen-vagrant code analysis shows 0 unresolved vulnerabilities.
              There are 0 security hotspots that need review.

            kandi-License License

              kitchen-vagrant has a Non-SPDX License.
              Non-SPDX licenses can be open source with a non SPDX compliant license, or non open source licenses, and you need to review them closely before use.

            kandi-Reuse Reuse

              kitchen-vagrant releases are available to install and integrate.
              Installation instructions are not available. Examples and code snippets are available.
              kitchen-vagrant saves you 904 person hours of effort in developing the same functionality from scratch.
              It has 2064 lines of code, 39 functions and 5 files.
              It has high code complexity. Code complexity directly impacts maintainability of the code.

            Top functions reviewed by kandi - BETA

            kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
            Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of kitchen-vagrant
            Get all kandi verified functions for this library.

            kitchen-vagrant Key Features

            No Key Features are available at this moment for kitchen-vagrant.

            kitchen-vagrant Examples and Code Snippets

            No Code Snippets are available at this moment for kitchen-vagrant.

            Community Discussions

            QUESTION

            Could not load the 'vagrant' driver from the load path Test Kitchen, downloading new versions doesn't work
            Asked 2020-Feb-11 at 18:21

            When I try to run kitchen test on terminal I'm greeted with

            ...

            ANSWER

            Answered 2020-Feb-11 at 18:21

            I 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.

            Source https://stackoverflow.com/questions/58956099

            QUESTION

            With vagrant-berkshelf deprecated, will it be possible to drive builds from Vagrant, with Chef solely as a provisioner?
            Asked 2018-Feb-28 at 21:45

            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 Vagrantfiles, 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:45

            It 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.

            Source https://stackoverflow.com/questions/49038059

            QUESTION

            Vagrant ubuntu/trusty64 contains old version of Ruby which causes test-kitchen to fail
            Asked 2018-Jan-04 at 21:30

            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:30

            Thanks to Hubert above, I changed

            this

            Source https://stackoverflow.com/questions/48050783

            QUESTION

            Chef environment concepts
            Asked 2017-May-29 at 07:06

            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:26

            Roles 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 :) ):

            Source https://stackoverflow.com/questions/44154984

            QUESTION

            Test Kitchen Vagrant Berkshelf
            Asked 2017-Apr-17 at 02:44

            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:44

            Berkshelf 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.

            Source https://stackoverflow.com/questions/43403262

            Community Discussions, Code Snippets contain sources that include Stack Exchange Network

            Vulnerabilities

            No vulnerabilities reported

            Install kitchen-vagrant

            You can download it from GitHub.
            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

            For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .
            Find more information at:

            Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items

            Find more libraries
            CLONE
          • HTTPS

            https://github.com/test-kitchen/kitchen-vagrant.git

          • CLI

            gh repo clone test-kitchen/kitchen-vagrant

          • sshUrl

            git@github.com:test-kitchen/kitchen-vagrant.git

          • Stay Updated

            Subscribe to our newsletter for trending solutions and developer bootcamps

            Agree to Sign up and Terms & Conditions

            Share this Page

            share link