Add no_proxy config value to docker-compose.yml 77/65577/1
authorVictor Morales <victor.morales@intel.com>
Mon, 10 Sep 2018 09:19:43 +0000 (02:19 -0700)
committerVictor Morales <victor.morales@intel.com>
Mon, 10 Sep 2018 09:24:08 +0000 (02:24 -0700)
commite7a7b50f6fc0f036eeb116f95e8e5fb8d56aa4ef
treeddb30ce6aae8e593f8c6d03f51e2c2058bd6bf21
parent5b6f0c4efbfdc0c9bcb440c8da132bdaee4e518d
Add no_proxy config value to docker-compose.yml

The no_proxy configuration value was missing in the docker-compose.yml
this was causing a different behaviour when the functional tests were
running and consuming the services on the container.

Change-Id: Ie88e88d50e0ec9c4aa0d03367f2a9d25edccb753
Signed-off-by: Victor Morales <victor.morales@intel.com>
Issue-ID: MULTICLOUD-301
deployments/docker-compose.yml
src/k8splugin/Gopkg.lock
src/k8splugin/api/handler.go
src/k8splugin/db/consul.go
vagrant/installer.sh
vagrant/tests/plugin.sh