forked from chef-boneyard/vagrant-omnibus
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Setting for the proxy environment - isolated change
- Loading branch information
kbarczyn
committed
Jul 16, 2013
1 parent
e63734b
commit b692d9e
Showing
1 changed file
with
13 additions
and
2 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
b692d9e
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.
@kbarczyn @schisamo I don't think we can use
ENV['http_proxy']
here. This is evaluated on the host, not the vagrant vm, and the vagrant vm does not necessarily have the same proxy settings as the host. This might be the case for a local virtualbox vm, but not for a vagrant vm in the cloud (e.g. via vagrant-aws or vagrant-rackspace).Suggestion: it should either be a separate env var on the host, e.g.
VAGRANT_HTTP_PROXY
, or it should be a configuration option of vagrant-omnibus.b692d9e
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.
btw: as a workaround I tried configuring the proxy on the VM via a shell provisioner first, but this does not work because vagrant-omnibus kicks in before any provisioner.
@schisamo would it be possible to hook in vagrant-omnibus specifically before the
:chef_client
and:chef_solo
provisioners, so that other provisioners can without vagrant-omnibus kicking in?b692d9e
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.
Doesn't work:
The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!
export http_proxy=XXX:8080
export https_proxy=XXX:8080
b692d9e
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.
@sprevha: I was using it successfully. Vagrant doesn't want to start? You get exception when starting?
I like the option with VAGRANT_HTTP_PROXY.
b692d9e
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.
@kbarczyn @schisamo
VAGRANT_ENV_HTTP_PROXY
as the name for the environment variable would be in line with tmatilai/vagrant-proxyconf#6