edgexfoundry / core-config-seed Goto Github PK

In launch-consul-config.sh

if [ -z $ARCH ]
then
rm -rf /consul/data/* && docker-entrypoint.sh agent $CONSUL_ARGS | tee /edgex/logs/core-consul.log &
else
rm -rf /consul/data/* && $APP_DIR/docker-entrypoint.sh agent $CONSUL_ARGS | tee /edgex/logs/core-consul.log &
fi

The script causes the Consult data cannot be persisted. Reproduce steps:

1. docker-compose up -d volume
2. docker-compose up -d config-seed
3. create or change anything in key/value store
4. docker-compose restart config-seed
5. everything you created or changed disappears

It should the expected behavior

Stretch goal for California Preview (to be done by Samsung)

The current config seed loads all of its configs when it runs, including all existing device services (as of Barcelona release). It also always loads both the docker and non-docker config for each service. I originally ran into this while working on my edgex core snap, but managed to reproduce as well by starting up the default Barcelona services via the developer-script run-it script.

Application.properties uses Unix absolute path for logging.file, breaks on Windows when running from source with error:

log4j:ERROR setFile(null,true) call failed.
java.io.FileNotFoundException: /edgex/logs/edgex-core-metadata.log (No such file or directory)

all the service ids contain "edgex-" prefix, such as edgex-core-data.
however, the current config seed path all look like config/core-data/, not config/edgex-core-data/
thus, the configuration won't be loaded by each services

2017/11/08 10:38:07 [WARN] agent: Check 'service:edgex-support-rulesengine-docker-48075' is now critical
2017/11/08 10:38:07 [WARN] agent: Check 'service:edgex-support-logging-docker-48061' is now critical
2017/11/08 10:38:08 [WARN] agent: Check 'service:edgex-export-distro-docker-48070' is now critical
2017/11/08 10:38:09 [WARN] agent: Check 'service:edgex-support-scheduler-docker-48085' is now critical
2017/11/08 10:38:11 [WARN] agent: Check 'service:edgex-export-client-docker-48071' is now critical
2017/11/08 10:38:13 [WARN] agent: Check 'service:edgex-device-virtual-docker-49990' is now critical
2017/11/08 10:38:13 [WARN] agent: Check 'service:edgex-core-metadata-docker-48081' is now critical
2017/11/08 10:38:16 [WARN] agent: Check 'service:edgex-core-data-docker-48080' is now critical
2017/11/08 10:38:16 [WARN] agent: Check 'service:edgex-core-command-docker-48082' is now critical
2017/11/08 10:38:17 [WARN] agent: Check 'service:edgex-support-rulesengine-docker-48075' is now critical
2017/11/08 10:38:17 [WARN] agent: Check 'service:edgex-support-logging-docker-48061' is now critical
2017/11/08 10:38:18 [WARN] agent: Check 'service:edgex-export-distro-docker-48070' is now critical
2017/11/08 10:38:19 [WARN] agent: Check 'service:edgex-support-scheduler-docker-48085' is now critical
2017/11/08 10:38:21 [WARN] agent: Check 'service:edgex-export-client-docker-48071' is now critical
2017/11/08 10:38:23 [WARN] agent: Check 'service:edgex-device-virtual-docker-49990' is now critical
2017/11/08 10:38:23 [WARN] agent: Check 'service:edgex-core-metadata-docker-48081' is now critical
2017/11/08 10:38:26 [WARN] agent: Check 'service:edgex-core-data-docker-48080' is now critical
2017/11/08 10:38:26 [WARN] agent: Check 'service:edgex-core-command-docker-48082' is now critical
2017/11/08 10:38:27 [WARN] agent: Check 'service:edgex-support-rulesengine-docker-48075' is now critical
2017/11/08 10:38:27 [WARN] agent: Check 'service:edgex-support-logging-docker-48061' is now critical
2017/11/08 10:38:28 [WARN] agent: Check 'service:edgex-export-distro-docker-48070' is now critical