Adapt consul configuration for HV-VES

New configuration format will allow hv-ves to accept more routes
if needed.
Also fixes consul host name.

Change-Id: I869a78273cb961529aa2c7edfa129319c34dfb42
Issue-ID: DCAEGEN2-791
Signed-off-by: Filip Krzywka <filip.krzywka@nokia.com>

diff --git a/blueprints/k8s-hv-ves.yaml-template b/blueprints/k8s-hv-ves.yaml-template
index a042bfa..9bb6d32 100644 (file)
--- a/blueprints/k8s-hv-ves.yaml-template
+++ b/blueprints/k8s-hv-ves.yaml-template
@@ -45,7 +45,7 @@ inputs:
   consul_host:
     type: string
     description: Consul endpoint address
-    default: 'consul-server.onap-consul'
+    default: 'consul-server.onap'
   consul_port:
     type: integer
     description: Consul endpoint port
@@ -75,8 +75,8 @@ node_templates:
       application_config:
         dmaap.kafkaBootstrapServers: { get_input: kafka_bootstrap_servers }
         collector.routing:
-            fromDomain: { get_input: hv_meas_domain }
-            toTopic: { get_input: hv_meas_kafka_topic }
+            - fromDomain: { get_input: hv_meas_domain }
+              toTopic: { get_input: hv_meas_kafka_topic }
       docker_config:
         healthcheck:
           endpoint: /health/ready