Repository navigation
ci: run Ideas Board multi-region IT against a docker-compose cluster - #8
Merged
Merged
Conversation
Add a 3-region (us-east1/us-west1/us-central1) docker-compose cluster and a dedicated examples-it-multiregion workflow so test_regional_it.py actually executes instead of skipping. The one-shot crdb-init service inits the cluster, waits for all regions, and makes defaultdb multi-region; the job then installs the published packages and runs only the regional IT with CRDB_MULTIREGION=true and CRDB_URL pointed at node1. Mirrors the proven Go repo setup. The existing examples-it.yml (single-node Testcontainers) is untouched.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Makes the Ideas Board multi-region integration test (
examples/ideas-board/test_regional_it.py) actually run in CI instead of skipping.examples/ideas-board/multiregion-compose.yml— 3-node insecure CockroachDB cluster, one node per region via--locality(us-east1,us-west1,us-central1),--joinmesh, on-disk ephemeral stores,--cache=256MiB --max-sql-memory=256MiB. One-shotcrdb-initrunscockroach init, waits for all 3 regions, thenALTER DATABASE defaultdb SET PRIMARY REGION+ADD REGION. Only node1 publishes:26257..github/workflows/examples-it-multiregion.yml— up -d →timeout 420 docker compose run --rm crdb-init→pip install -r requirements.txt→pytest test_regional_it.py -vwithCRDB_MULTIREGION=trueandCRDB_URL=postgres://root@localhost:26257/defaultdb?sslmode=disable. Dumps cluster logs on failure,down -valways.Mirrors the proven Go repo setup (
cockroachdb-go-library). The existing single-node Testcontainers workflow (examples-it.yml) is untouched; the regional IT still skips there.Verification
Ran locally against the compose cluster (colima):
crdb-initconfigureddefaultdbas multi-region (us-east1 primary + us-west1 + us-central1) and the test passed — rows homed correctly in us-east1 and us-west1 via the hiddencrdb_regioncolumn. No library or demo bug found.