2.4.0 dns based discovery of deployment-handler

- policy-handler uses dns based discovery of
   deployment-handler - driven by config
- new data structure for deploy_handler section of config
    --  changed from string "deployment_handler" in 2.3.1
         to structure in 2.4.0
    deploy_handler :
        # name of deployment-handler service
        #     used by policy-handler for logging
        target_entity : "deployment_handler"
        # url of the deployment-handler service
        # for policy-handler to direct the policy-updates to
        #   - expecting dns to resolve the name
        #      deployment_handler to ip address
        url : "http://deployment_handler:8188"

- logic is backwards compatible with 2.3.1 format
- removed import pip from audit
   -- import pip broken in pip 9.0.2 (2018-03-19)
   -- import pip conflicts with requests
   -- pip API is not officially supported
   -- see links for more
      https://github.com/pypa/pip/issues/5079
      https://github.com/pypa/pip/issues/5081

Change-Id: Ifcaba6cfd714f3099ab7a25fe979a3696a6460fc
Signed-off-by: Alex Shatov <alexs@att.com>
Issue-ID: DCAEGEN2-404

1 files changed, 4 insertions, 1 deletions

diff --git a/etc_upload/config.json b/etc_upload/config.json
index 920ef7c..1350b37 100644
--- a/etc_upload/config.json
+++ b/etc_upload/config.json
@@ -23,6 +23,9 @@
             },
             "target_entity" : "policy_engine"
         },
-        "deploy_handler" : "deployment_handler"
+        "deploy_handler" : {
+            "target_entity" : "deployment_handler",
+            "url" : "http://deployment_handler:8188"
+        }
     }
 }