Adding a second Test configuration when using FIWARE components inside Docker

Question

Adding a second Test configuration when using FIWARE components inside Docker

Closed this issue 5 months ago · 1 comments

There is currently the problem that not all tests run through when working inside a local Docker environment. This occurs in most cases with subscriptions, as the containers cannot communicate with each other via localhost. For example, you cannot send an MQTT subscription to the URL mqtt://127.0.0.1:1883, but must send it to mqtt://<mosquitto container hostname>:1883 in the case of Docker. There is no bug, but it would be useful if there was a second test config file for such URLs (of each FIWARE component).

Answer 1 · 2024-02-06T10:01:49.000Z

Branch 238-Adding-a-second-Test-configuration-when-using-FIWARE-components-inside-Docker created!