DongHyeonkaandClaude Opus 5
5f10b791d3
Snapshot of the in-flight state that already existed, identically, in both this worktree and the main checkout before this session began: the initial HTTP Client platform implementation (previously untracked), the redis-lab removal, and the JPA / object-storage / notification integration work. Kept separate from this session's HTTP Client review response, which lands in the following commit, so the two bodies of work stay reviewable apart. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
27 lines
905 B
YAML
27 lines
905 B
YAML
# Standalone lane for the Redis SDK topology tests.
|
|
#
|
|
# The version is a build argument rather than a pinned image so the same file serves every row of
|
|
# the support matrix. Nothing here is a production topology: no persistence, no TLS, no replication.
|
|
# It exists to answer "does the driver behave the way the SDK claims", which is a question the
|
|
# in-memory fixture cannot answer at all.
|
|
services:
|
|
redis:
|
|
image: "redis:${REDIS_VERSION:-7.4}"
|
|
command:
|
|
- redis-server
|
|
- --appendonly
|
|
- "no"
|
|
- --save
|
|
- ""
|
|
- --aclfile
|
|
- /etc/redis/acl/all-accounts.acl
|
|
volumes:
|
|
- ../acl:/etc/redis/acl:ro
|
|
ports:
|
|
- "${REDIS_PORT:-6379}:6379"
|
|
healthcheck:
|
|
test: ["CMD-SHELL", "[ \"$$(redis-cli --user ca-skeleton-application --pass fixture-application --no-auth-warning ping)\" = PONG ]"]
|
|
interval: 2s
|
|
timeout: 2s
|
|
retries: 15
|