Per T328969: AQS 2.0: Revisit in-service testing approach, we are refactoring in-service tests to separate "unit" tests, which have no external dependencies, from "integration" tests, which may depend on a datastore external to the service
As part of this, we expect to spin up the Cassandra testing environment as a late stage in CI, after merge but before image tagging for actual deployment.
Our current Cassandra testing env is not well suited for this, for at least the following reasons:
- it lives within a personal repo
- it requires a multi-step startup process that involves watching for a console message
Investigate the actual requirements, likely in conjunction with SRE and Release Engineering, and refactor as necessary.This will almost certainly involve creating a new repo for the env.