zeekay fb1166c5f5 test(e2e): run KV, not an upstream Redis container ...

The gateway test started redis:8.4.0 through the testcontainers redis module
and connected with go-redis. It now starts ghcr.io/hanzoai/kv and connects with
github.com/hanzokv/go, so the e2e suite exercises the server we ship.

The client is built from the container's host and mapped port rather than from
its connection string. Our ParseURL accepts kv:// only, and a mapped port is
host:port anyway — the URL was a detour.

reset_redis.go is reset_kv.go; the PAM resource type is left as the generated
client names it, because it names the external system being connected to,
alongside kubernetes.

Verified: go build ./... and go vet ./relay/... ./packages/... both clean.

2026-07-26 16:34:30 -07:00

..

compose.go

rebrand: purge Infisical completely (identifiers, env vars, strings, e2e, dirs)

2026-06-20 21:35:35 -07:00

reset.go

test(e2e): run KV, not an upstream Redis container

2026-07-26 16:34:30 -07:00