Replace custom integration runner in vdev
with compose
#17051
Labels
domain: vdev
Anything related to the vdev tooling
type: tech debt
A code change that does not add user value.
The original integration test setup had a
runner
block in every docker compose file with nearly identical contents. The reworked setup used byvdev
removed that duplication and moved it into the tool by setting up a custom runner outside of docker compose. Unfortunately, this has created considerable complication withinvdev
for managing that setup external to the main docker-compose containers.With #17025, we will have a framework for injecting bits into the compose files before they containers are built. We should use this capability to set up a standardized
runner
block and run the entire network of containers withindocker-compose
. This will simplify running integration tests invdev
and allow us to remove all the code specialized on handling the test runner separately.The text was updated successfully, but these errors were encountered: