Skip to content
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

Open
scottschreckengaust opened this issue Oct 1, 2020 · 6 comments
Open

asdf install vagrant <version> Fails #15

scottschreckengaust opened this issue Oct 1, 2020 · 6 comments

Comments

@scottschreckengaust
Copy link

❯ asdf --version
v0.8.0
❯ asdf plugin list --urls --refs | grep vagrant
vagrant                      https://github.com/Banno/asdf-hashicorp.git master 4bd2904
❯ asdf list vagrant
  No versions installed
❯ asdf list all vagrant
1.4.0
...
2.2.10
❯ asdf install vagrant latest
Downloading vagrant version 2.2.10 from https://releases.hashicorp.com/vagrant/2.2.10/vagrant_2.2.10_darwin_amd64.zip
Error: vagrant version 2.2.10 not found
❯ asdf install vagrant 2.2.10
Downloading vagrant version 2.2.10 from https://releases.hashicorp.com/vagrant/2.2.10/vagrant_2.2.10_darwin_amd64.zip
Error: vagrant version 2.2.10 not found
❯ asdf install vagrant 1.4.0
Downloading vagrant version 1.4.0 from https://releases.hashicorp.com/vagrant/1.4.0/vagrant_1.4.0_darwin_amd64.zip
Error: vagrant version 1.4.0 not found

At https://www.vagrantup.com/downloads.html, I noticed that the MacOS download points to x86_64.dmg instead of darwin_amd64.zip at https://releases.hashicorp.com/vagrant/2.2.10/vagrant_2.2.10_x86_64.dmg, could this be the issue?

@scottschreckengaust
Copy link
Author

FYI: packer and terraform work (didn't try any others)

@denizdogan
Copy link

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.

@scottschreckengaust
Copy link
Author

derive a different location based on system architecture...

https://github.com/Banno/asdf-hashicorp/blob/master/bin/install#L50-L54

loganlinn added a commit to loganlinn/asdf-plugins that referenced this issue Apr 7, 2021
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.
@DustinChaloupka
Copy link
Contributor

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.

@DustinChaloupka
Copy link
Contributor

The releases made for vagrant are quite a bit different from the other packages that this plugin supports. The linux .zip file does exist for newer releases, but that's the only one. We do not have any plans to add actual support for installing vagrant currently. This plugin is getting moved to the asdf-community, so maybe someone will be willing to add support. @radditude might also have some ideas on getting releases to be the same as other Hashicorp tools?

@jthegedus
Copy link

Sharing my comment here also:

asdf plugins are intended to support 1 tool and any number of binaries installed by said tool. The association is plugin:tool:binaries=1:1:*. This is because the asdf plugin lifecycle hooks are supposed to allow modifications to the usage of specific binaries installed by the plugin.

Maintenance becomes a burden which spawns plugins like this. For the most part they work, but prefer more specific plugins where available.

jthegedus added a commit to asdf-vm/asdf-plugins that referenced this issue Apr 16, 2021
* 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]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

4 participants