Instead of specifying KafkaBootstrap servers by means of Consul
configuration use command line options / environment. DMaaP MR endpoint
should not be changed frequently so keeping this in runtime
configuration (refreshed during application runtime) won't make much
sense. This will also clean up internal HV-VES architecture.
Change-Id: I89e8101cd0591b3f74df53be9114b1a0d5fbb905
Issue-ID: DCAEGEN2-1047
Signed-off-by: Piotr Jaszczyk <piotr.jaszczyk@nokia.com>
{ concat: [ { get_input: container_port }, '' ] }
VESHV_HEALTH_CHECK_API_PORT:
{ concat: [ { get_input: healthcheck_port }, '' ] }
+ VESHV_KAFKA_BOOTSTRAP_SERVERS:
+ { get_input: kafka_bootstrap_servers }
VESHV_SSL_DISABLE: ''
properties:
application_config:
- dmaap.kafkaBootstrapServers: { get_input: kafka_bootstrap_servers }
collector.routing:
- fromDomain: { get_input: perf3gpp_domain }
toTopic: { get_input: perf3gpp_kafka_topic }