-
Notifications
You must be signed in to change notification settings - Fork 200
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
force Vagrant to use the "new" API URL #1893
Conversation
I have filed https://bugzilla.redhat.com/show_bug.cgi?id=2337302 but do not expect much movement, given the state of Vagrant. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Initially @ianballou also found this in #1859 but I see that part has now been reverted again.
9d70932
to
cc3a0f9
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we force this in our wrapper instead so it benefits local uses as well? We already have some:
Lines 5 to 6 in e7a0f21
ENV['LANG'] = 'en_US.UTF-8' | |
ENV['LC_ALL'] = 'en_US.UTF-8' |
So I'd suggest
ENV['VAGRANT_SERVER_URL'] ||= https://vagrantcloud.com/api/v2/vagrant
Or would you prefer to avoid that for people who have moved to the new client?
I haven't tested if that works, but have no objection doing so there. |
Tested. This is actually better, as it also fixes |
It seems Vagrant has introduced a new API and their proprietary client does use that by default now, so they turned off the old one (or the redirect, I really have no idea what was there last week). Just setting the new URL (which I found out by using `vagrant --debug`) as the server URL works for now, so let's do that, and at least unblock nightlies.
cc3a0f9
to
b63db33
Compare
It seems Vagrant has introduced a new API and their proprietary client
does use that by default now, so they turned off the old one (or the
redirect, I really have no idea what was there last week).
Just setting the new URL (which I found out by using
vagrant --debug
)as the server URL works for now, so let's do that, and at least unblock
nightlies.