Removed all http_proxy reference from build. 43/97743/1
authorSebastien Premont-Tendland <sebastien.premont@bell.ca>
Tue, 29 Oct 2019 21:32:54 +0000 (17:32 -0400)
committerSebastien Premont-Tendland <sebastien.premont@bell.ca>
Wed, 30 Oct 2019 14:06:54 +0000 (10:06 -0400)
commit2703d7ab7045089a381416d6e3b15df5f7e785ef
tree88ac98496b3120113f006e5c8510a1765f00e7b8
parent129cc5bd7654b8017c22f53ebd6cbf9f1b12f55e
Removed all http_proxy reference from build.
http_proxy is an environment configuration and should not be defined in
in the build script.
If you need to use a proxy to build docker images then add it to
the mvn command like this :

-Ddocker.buildArg.http_proxy=$PROXY -Ddocker.buildArg.https_proxy=$PROXY

Also adding http_proxy in the Dockerfile directly will add the
environment variable in the POD statically using the proxy the was
built with at runtime.

If a proxy is needed at runtime then the environment variables should be
injecting using helm charts and overrides.

Issue-ID: CCSDK-1877
Signed-off-by: Sebastien Premont-Tendland <sebastien.premont@bell.ca>
Change-Id: I2b99b277b594408c974cf29a5804384293776a22
ms/blueprintsprocessor/application/pom.xml
ms/blueprintsprocessor/application/src/main/docker/Dockerfile
ms/command-executor/src/main/docker/Dockerfile
ms/py-executor/docker/Dockerfile
ms/sdclistener/distribution/src/main/docker/Dockerfile