Fully HTTPS support in the dcaedt-be

Fully HTTPS support:
-Updated the onap/base_sdc-jetty docker image version
-Updated the chef script to properly used of the new docker image
-Updated jvm configuration to support call to
the SDC components using HTTPS.
-Add support for change the http to https in the python script
-Added buildRestClient method to create the CloseableHttpClient
supporting the SSL connection
-Checkstyle in the recipes
-Update the docker_run.sh:
  - Change JAVA_OPTIONS
  - Used the secure connection to do health check

Issue-ID: SDC-2477
Signed-off-by: Krystian Kedron <k.kedron@partner.samsung.com>
Change-Id: I7bf3d307e5765fa75a37ba0a4b41fd7fa87d28ab

1 files changed, 0 insertions, 13 deletions

diff --git a/docker/docker_be/chef-solo/cookbooks/Deploy-DCAE/README.md b/docker/docker_be/chef-solo/cookbooks/Deploy-DCAE/README.md
deleted file mode 100644
index 5d1fd04..0000000
--- a/docker/docker_be/chef-solo/cookbooks/Deploy-DCAE/README.md
+++ /dev/null
@@ -1,13 +0,0 @@
-# Deploy-DCAE
-
-1. default.rb = file that defines default to parameters used inside the cookbook
-2. recipes/dcae_setup.rb = create and configure application.properties and logback-spring.xml using template defined in dcae-application.properties.erb with values from defaults.rb or from environments.json
-3. recipes/jetty_setup.rb = configure the jetty (ssl)
-4. roles/dcae-fe.json = chef roles (which recipe to run)
-5. Dockerfile = SDC Base line jettystartup.sh = run all of the above and run docker-entrypoint.sh that starts the jetty
-6. pom.xml = docker profile.
-			 tag for onap
-			 build-helper-maven-plugin = extract version from the war
-			 maven-resources-plugin - copy the war to docker/target
-			 docker-maven-plugin = creates the docker - configured with the dockerFile location
-