Hi,
recently we were fixing the util function for checking if tests are executed in a container. If doing this I believe that other services are involved quite often. Thus the tests executing container must be able to communicate with those services. To be able to do that it's common practice that containers are in the same network, so the executing container must be added to the network of the service containers as well.
It may be a little bit out of scope, but at least I consider it as something that's needed in lot of the use cases. So I had to provide such a function anyway. Would it be a useful addition to add another function in the util package that's able to retrieve the own container ID?
Regards
Alex
Hi,
recently we were fixing the util function for checking if tests are executed in a container. If doing this I believe that other services are involved quite often. Thus the tests executing container must be able to communicate with those services. To be able to do that it's common practice that containers are in the same network, so the executing container must be added to the network of the service containers as well.
It may be a little bit out of scope, but at least I consider it as something that's needed in lot of the use cases. So I had to provide such a function anyway. Would it be a useful addition to add another function in the util package that's able to retrieve the own container ID?
Regards
Alex