Closed FelixTing closed 1 year ago
- Also we don't create a device-bacnet-ip secret store token, nor a registry role, nor propagate the redis secret (not sure if that is needed).
Changes in this PR should take care of these: https://github.com/edgexfoundry/edgex-compose/pull/398/files
Also we don't mount /tmp/edgex/secrets/device-bacnet-ip to the container
Same but need to make sure it has -ip
๐ Bug Report
Affected Services [REQUIRED]
The issue is located in: device-bacnet ### Is this a regression? Yes, the previous version in which this bug was not present was: .... ### Description and Minimal Reproduction [**REQUIRED**] In device-bacnet-c, service key is either `device-bacnet-ip` or `device-bacnet-mstp`. https://github.com/edgexfoundry/device-bacnet-c/blob/de54976e2d34757b5269fc827b494d0b9848b55d/src/c/main.c#L631-L644 However, the service key used in the compose-builder Makefile is device-bacnet. https://github.com/edgexfoundry/edgex-compose/blob/bf8c3022642096ec20f4ad6147e719a0404d0ccb/compose-builder/Makefile#L155-L177 This results in the device service being unable to locate the required SecretStore token, Consul token, and MessageBus credentials. related issue: https://github.com/edgexfoundry/device-bacnet-c/issues/74 ## ๐ฅ Exception or Error๐ Your Environment
Deployment Environment: ubuntu 22.04 LTS
EdgeX Version [REQUIRED]: minnesota dev
Anything else relevant?