Vagrant version 2.4.2 introduced a patch(512bb74) that sets the logger gem dependency to "~>1.6.1", which is too strict and prevents many Vagrant plugins from being installed.
This patch tones down the dependency specification to mitigate this problem.
Fixes#13527.
Refer-to: Add logger and ostruct to the gemspec by hswong3i · Pull Request #13499 · hashicorp/vagrant <https://github.com/hashicorp/vagrant/pull/13499>
base64 will no longer be the default gem in the Ruby 3.4, without this
patch following warning message may come from ruby 3.3+
/opt/vagrant/lib/vagrant/util/powershell.rb:4: warning: base64 was
loaded from the standard library, but will no longer be part of the
default gems since Ruby 3.4.0. Add base64 to your Gemfile or gemspec.
See https://github.com/thinreports/thinreports-generator/pull/134
Signed-off-by: Wong Hoi Sing Edison <hswong3i@pantarei-design.com>
Updates the vagrant_cloud dependency constraint to a minimum of 3.1.1
which includes a path prefixing fix that resolves an issue affect direct
uploads to Vagrant Cloud.
Introduce support for handling box architecture. Adds a new
`box_architecture` setting that defaults to `:auto` which will perform
automatic detection of the host system, but can be overridden with a
custom value. Can also be set to `nil` which will result in it fetching
the box flagged with the default architecture within the metadata.
Box collection has been modified to allow existing boxes already
downloaded and unpacked to still function as expected when architecture
information is not available.
Adds initial basic support for HCP based configuration in vagrant-go.
The initalization process has been updated to remove Vagrantfile parsing
from the client, moving it to the runner using init jobs for the basis
and the project (if there is one). Detection is done on the file based
on extension for Ruby based parsing or HCP based parsing.
Current HCP parsing is extremely simple and currently just a base to
build off. Config components will be able to implement an `Init`
function to handle receiving configuration data from a non-native source
file. This will be extended to include a default approach for injecting
defined data in the future.
Some cleanup was done in the state around validations. Some logging
adjustments were applied on the Ruby side for better behavior
consistency.
VirtualBox provider now caches locale detection to prevent multiple
checks every time the driver is initialized.
Add configuration file for automated license modifications, remove
automated licese modifications from specific locations, and update the
license set in the gem specification.
With existing layout the built shared library will end up in the `./lib`
directory, but the expected location being checked is `./lib/vagrant`.
Adjusting the path within the extension directory results in the proper
adjustment to the installation path.
On OpenSSL 3, engines have been deprecated being replaced by providers.
The Ruby openssl library supported loading specific engines, but there
is no replacement currently using providers. The winrm communicator
specifically relies on a MD4 which OpenSSL has marked as legacy and no
longer loads by default.
The extension included loads the legacy provider as well as the default
provider. The legacy provider includes MD4, thus allowing winrm to
function again.
This ensures that we get the Ruby 3 keywords support that landed in that
version https://github.com/rspec/rspec-mocks/pull/1394
Unfortunately this does not magically fix our test failures, just
ensures that expectations are being handled properly across Ruby
versions going forward.
