public final class YugabyteDBYSQLWaitStrategy
extends org.testcontainers.containers.wait.strategy.AbstractWaitStrategy
Though we can either use HTTP or PORT based wait strategy, when we create a custom database/role, it gets executed asynchronously. As the wait on container.start() on a specific port wouldn't fully guarantee the custom object execution. It's better to check the DB status with this way with a smoke test query that uses the underlying custom objects and wait for the operation to complete.
| Constructor and Description |
|---|
YugabyteDBYSQLWaitStrategy(org.testcontainers.containers.wait.strategy.WaitStrategyTarget target) |
| Modifier and Type | Method and Description |
|---|---|
void |
waitUntilReady() |
void |
waitUntilReady(org.testcontainers.containers.wait.strategy.WaitStrategyTarget target) |
public YugabyteDBYSQLWaitStrategy(org.testcontainers.containers.wait.strategy.WaitStrategyTarget target)
public void waitUntilReady(org.testcontainers.containers.wait.strategy.WaitStrategyTarget target)
waitUntilReady in interface org.testcontainers.containers.wait.strategy.WaitStrategywaitUntilReady in class org.testcontainers.containers.wait.strategy.AbstractWaitStrategypublic void waitUntilReady()
waitUntilReady in class org.testcontainers.containers.wait.strategy.AbstractWaitStrategy