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

Configuring Chef provisioners fails if a proxy is set to false #24

Closed
tmatilai opened this issue Sep 12, 2013 · 1 comment
Closed

Configuring Chef provisioners fails if a proxy is set to false #24

tmatilai opened this issue Sep 12, 2013 · 1 comment
Labels

Comments

@tmatilai
Copy link
Owner

The plugin errors out with e.g. config.proxy.http = false:

[default] Configuring proxy for Chef provisioners...
/Applications/Vagrant/embedded/lib/ruby/1.9.1/uri/common.rb:176:in `split': bad URI(is not URI?): false (URI::InvalidURIError)
    from /Applications/Vagrant/embedded/lib/ruby/1.9.1/uri/common.rb:211:in `parse'
    from /Applications/Vagrant/embedded/lib/ruby/1.9.1/uri/common.rb:747:in `parse'
    from /Users/tmatilai/.vagrant.d/gems/gems/vagrant-proxyconf-0.5.0/lib/vagrant-proxyconf/config/proxy.rb:54:in `user'
    from /Users/tmatilai/.vagrant.d/gems/gems/vagrant-proxyconf-0.5.0/lib/vagrant-proxyconf/config/proxy.rb:33:in `http_user'
    from /Users/tmatilai/.vagrant.d/gems/gems/vagrant-proxyconf-0.5.0/lib/vagrant-proxyconf/action/configure_chef_proxy.rb:57:in `configure_chef'
@tmatilai
Copy link
Owner Author

If someone is hitting this before the next release, the workaround is to use empty string "" instead of false.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant