You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Improve TC-python feature parity with TC-java by enabling container to specify dependsOn, which should work similar to how depends_on in docker-compose does - container B that depends on container A won't be started until container A is in running state.
Why should it be done this way?
Control order/behavior for container startup in multi-container scenarios.
Other references:
Include any other relevant reading material about the enhancement.
The text was updated successfully, but these errors were encountered:
I have implemented the depends_on functionality for DockerContainer, mirroring the dependsOn behavior in TC-java so that dependent containers only start once their dependencies are in the running state. The PR for this enhancement is now open: #728. Please check it out, and let me know if any changes are needed.
What are you trying to do?
Improve TC-python feature parity with TC-java by enabling container to specify
dependsOn
, which should work similar to howdepends_on
in docker-compose does - container B that depends on container A won't be started until container A is inrunning state
.Why should it be done this way?
Control order/behavior for container startup in multi-container scenarios.
Other references:
Include any other relevant reading material about the enhancement.
The text was updated successfully, but these errors were encountered: