Configure local develop env to use Temporal auto-setup for configurability#202
Configure local develop env to use Temporal auto-setup for configurability#202
Conversation
| TEMPORAL_A_VERSION=1.29.4 | ||
| TEMPORAL_B_VERSION=1.22.7 |
There was a problem hiding this comment.
example values - but these can connect ! (didn't validate a full replica)
| # Infrastructure versions | ||
| # TODO: currently shared by both servers, this could be independent. | ||
| POSTGRESQL_VERSION=16 | ||
| ELASTICSEARCH_VERSION=7.17.27 |
There was a problem hiding this comment.
In future - could make this more configurable.
I think I'm avoiding making this too comprehensive. We'll need a more-robust test harness for validating version connectivity - and I don't think docker compose and shell scripts are the solution for that.
As a followup, I'll look into adding a testcontainers harness which iterates through Temporal Server versions (and later backend configurations) to validate different functionality (connectivity, unidirectional replica, bidirectional replica, etc)
| @echo 'Temporal server versions:' | ||
| @printf ' %-16s' 'temporal-a:' && \ | ||
| $(DOCKER_COMPOSE) exec -T temporal-a \ | ||
| sh -c 'temporal operator cluster describe --address $$(hostname -i):7233 -o json 2>/dev/null | awk -F\" "/(serverVersion|server_version)/{print \$$4}"' \ |
There was a problem hiding this comment.
serverVersion|server_version
For Temporal Server compatibility.
|
Sorry to be the bearer of bad news, but auto-setup images are deprecated now. Best not to switch to them. |
|
Bummer! |
3 participants
What was changed
docker composenow usestemporalio/auto-setupinstead oftemporalio/temporaldev server.docker composeis split into multiple files, which are merged at exec time.Why?
temporalio/temporaldev server didn't give configurability. This setup will facilitate more robust local manual testing