-
-
Notifications
You must be signed in to change notification settings - Fork 54
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
asdf install vagrant <version>
Fails
#15
Comments
FYI: |
I have the same problem. Looking at https://releases.hashicorp.com/vagrant/2.2.10/ it looks like they don't have any zip builds for macOS, I guess they stopped providing them for some reason? I have no idea how one would solve this without building Vagrant from source using Ruby. |
derive a different location based on system architecture... https://github.com/Banno/asdf-hashicorp/blob/master/bin/install#L50-L54 |
This plugin has an issue installing vagrant (asdf-community/asdf-hashicorp#15) and isn't being actively maintained. Proposing it be removed to avoid a dead-end experience for users.
This might take a little bit of strange logic since it looks like vagrant uses different release names than the other common tools this supports, but I can take a look. |
The releases made for |
Sharing my comment here also:
Maintenance becomes a burden which spawns plugins like this. For the most part they work, but prefer more specific plugins where available. |
* Remove vagrant This plugin has an issue installing vagrant (asdf-community/asdf-hashicorp#15) and isn't being actively maintained. Proposing it be removed to avoid a dead-end experience for users. * fix: remove vagrant from readme Co-authored-by: James Hegedus <[email protected]>
At https://www.vagrantup.com/downloads.html, I noticed that the MacOS download points to
x86_64.dmg
instead ofdarwin_amd64.zip
at https://releases.hashicorp.com/vagrant/2.2.10/vagrant_2.2.10_x86_64.dmg, could this be the issue?The text was updated successfully, but these errors were encountered: