Use docker-compose to spin up a local CockroachDB cluster for testing

[ckoehn]

This changeset introduces a three node CockroachDB cluster for local testing. All interactions are steered through the Makefile to streamline the whole development process.

If a three node cluster is actually needed is up for discussion.

[ckoehn]

@gordthompson @rafiss Any interest in this change? Otherwise I will close it.

[gordthompson]

Thanks @ckoehn . This seems to be working fine for me. I have a bunch of little shell scripts that let me bounce around to different supported versions of CrDB and spin them up for testing so I'll probably continue to use those. However, this would be very convenient for someone with docker to test against a reasonably current backend version.

I notice that the version is currently pinned at v21.1.2 while the most recent version is (currently) v21.1.7. It might be nice to use

  image: cockroachdb/cockroach:latest

(if available) to keep people from getting stuck on an older version.

[ckoehn]

Thanks for the comment @gordthompson. I would prefer to pin it to a specific version instead of just latest to have a deterministic state. I was looking at the provided tags on docker hub and discovered latest-v21.1 which might be a good middle ground for this use case.

[rafiss]

thanks for this change!

[rafiss]

actually, before we merge this, could you document the usage for this in one of the READMEs?

[ckoehn]

Good idea! Will add it next week.

…

On 31. Aug 2021, at 06:36, Rafi Shamim ***@***.***> wrote:  actually, before we merge this, could you document the usage for this in one of the READMEs? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or unsubscribe. Triage notifications on the go with GitHub Mobile for iOS or Android.

[rafiss]

marking as "changes requested" for the README