All notable changes to this project will be documented in this file.
This project adheres to Semantic Versioning.
Standardise files with files in sous-chefs/repo-management
Standardise files with files in sous-chefs/repo-management
Standardise files with files in sous-chefs/repo-management
Standardise files with files in sous-chefs/repo-management
Standardise files with files in sous-chefs/repo-management
- Update default version to install to 2.3.4
- Logic fixes for installing >= 2.3.0
- CI and Cookstyle fixes
- Update tested platforms
- Standardize helper library and clean it up
- Cleanup and modernize unit tests
- Fix up generic installation
- Standardise files with files in sous-chefs/repo-management
- Standardise files with files in sous-chefs/repo-management
- Enabled
unified_mode
for all resources. - Dropped compatibility with Chef versions < 15.3.
- Updated Vagrant default version to 2.2.18 (previously was 2.2.4).
- Standardise files with files in sous-chefs/repo-management
- Standardise files with files in sous-chefs/repo-management
- resolved cookstyle error: metadata.rb:31:1 convention:
Layout/TrailingEmptyLines
- Install plugins in the root user home directory for inspec testing. The plugin location varies depending on environment variables unless explicitly set.
- Test using ubuntu 20.04
- Use build_essential to install vagrant-libvirt
- resolved cookstyle error: test/fixtures/cookbooks/wintest/resources/authorize_service.rb:11:1 warning:
ChefDeprecations/ResourceUsesOnlyResourceName
- Updated tests to work with root user (as is the case on docker machines)
- Style Fixes
- Simplify platform checks
- Migrated to Github Actions for testing
- Breaking change. Fail if Vagrant install is attempted on an unsupported OS.
- Add. Allow the install of the appimage version of Vagrant.
- Remove. Rubocop.yml doesn'tt need to protect the dangerfile any more.
- Change. Use the latest cookstyle rules
- Convert the resources to custom resources
- Add an env property to the plugin resource to allow for setting environment variables.
- Add an example of installing the vagrant-libvirt plugin, this plugin requires specific environment variable settings. See vagrant-libvirt/issues/891
- Add mac test instructions.
- Update the testing documentation
- Update the README to describe the new vagrant resource
- Create a custom resource to install vagrant. Fix issue #69
- Change the source respository name
- Add the authorize_service resource for setting up windows testing
- Use environment variable VAGRANT_HOME as the location to install plugins
- Add tests for chef-client 14
- Drop testing for chef-client 12
- Fix the calculation of the plugin directory location
- Fixes for Windows 2012R2:
- The Vagrant installer needs to reboot windows, but the MSI does this in a way that chef can't handle. As an alternative, we make chef interrupt itself and reboot the instance.
- Related to the above, the MSI returns two specific exit codes when it finishes (but not 0...) that chef needs to know about.
- Testing windows requires user 'vagrant' to hold the 'Replace a process level token' and 'Adjust Memory Quotas for a process' permissions. At the moment those setting must be made using the secpol.msc interface. A furtur task is to configure the vagrant user via the test cookbook.
- Vagrant version 1.9.7 suffers from the issue described in #82 (Expected process to exit with [0], but received '-1073741515'). For unknown reasons, this problem is resolved by using 2.0.3 (Perhaps also earlier versions, but they were not tested.)
- The package extension for the vagrant mac package changed. After version 1.9.2 the extension is _x86_64.dmg.
- The package extension for the vagrant windows package changed. After version 1.9.5 the extension is machinetype.msi.
- Added support for amazon linux
- Make the inspec tests run. Move them to the correct directories.
- Fixes for Chef 13 compat
- Install Vagrant 1.9.7 by default
- Fix #67: Remove depends constraint on Windows 1.x cookbook.
- Install Vagrant 1.8.5 by default
- Install Vagrant 1.8.1 by default
- Switch to InSpec verifier for test-kitchen
- Fix regression in
fetch_platform_checksums_for_version
method. Release 0.4.1 changed the checksums URL to the new Hashicorp location and introduced a regression. Thefetch_platform_checksums_for_version
method now returns the correct URL.
Thanks to Jeff Bachtel for the PR.
- Hashicorp has moved Vagrant package downloads from bintray.com to hashicorp.com. Download Vagrant packages from new location.
- Bump default Vagrant version to 1.7.4
- Cookbook no longer fails during compile phase if https://dl.bintray.com is unavailable. You can override
node['vagrant']['url']
andnode['vagrant']['checksum']
if you need to download Vagrant from a different location. - Fix idempotency when installing Vagrant Windows package.
- Refactor Vagrant::Helpers and add test coverage
vagrant_plugin
resource correctly installs vagrant plugins as another user on Windows.- Refactor LWRP and add unit tests.
- Add ChefSpec Custom Matchers
for
vagrant_plugin
. - Add Rakefile for testing/style checks.
- Add Travis-CI integration for style and unit tests
- Move vagrant_sha256sum mock to spec/support/shared_context.rb
- Refactor ChefSpec tests - move platform recipe specs into their own spec files
- #25, #31 Don't evaluate attributes on unsupported platforms
- #11 Custom plugin sources
- #14 Implement user-specific plugin installation
- #20, #21, Fix plugin version detection
- #28 Improve cross platform support
- Fix platform_family,
redhat
is not a family,rhel
is. (#18)
- Add
uninstall_gem
recipe to remove vagrant (1.0) gem.
- Initial release of vagrant