Skip to content
This repository has been archived by the owner on May 2, 2024. It is now read-only.

Provide vagrant 2.2.15 #11125

Closed
wants to merge 1 commit into from
Closed

Provide vagrant 2.2.15 #11125

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
33 changes: 33 additions & 0 deletions Casks/vagrant2-2-15.rb
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,33 @@
# This is provided because 2.2.16 has a bug where it cannot be used with
# RSA SHA1 ssh keys which makes it impossible to use with vagrant-aws as
# well as any other platform that only supports RSA SHA1 keys. There's
# been no activity from the vagrant maintainers to fix this so until
# something's done about it it should be easy to install 2.2.15.
#
# https://github.com/hashicorp/vagrant/issues/12344
cask "vagrant2-2-15" do
Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This particular tokenization is required by brew audit but it seems quite awkward. Is there any way to show it as 2.2.15?

version "2.2.15"
sha256 "5c2b290c4fa2371e255c56b1e96ded3d0c838d54cb7f0e8e6cf154e9f206a20e"

url "https://releases.hashicorp.com/vagrant/#{version}/vagrant_#{version}_x86_64.dmg",
verified: "hashicorp.com/vagrant/"
name "Vagrant"
desc "Development environment"
homepage "https://www.vagrantup.com/"

livecheck do
url "https://github.com/hashicorp/vagrant"
strategy :git
end

pkg "vagrant.pkg"

uninstall script: {
executable: "uninstall.tool",
input: ["Yes"],
sudo: true,
},
pkgutil: "com.vagrant.vagrant"

zap trash: "~/.vagrant.d"
end