Files
zeekayandHanzo Dev dead2da249 cd: the configuration speaks CD_ and KV_
The fork was already ours everywhere that matters — our image, our IAM (dex
is not deployed), hanzo kv behind what the env still called REDIS. Only the
vocabulary was upstream's: ARGOCD_* across the Go, the manifests, the docs
and the plugin contract, and mkdocs still titled 'Argo CD' pointing at
argoproj/argo-cd.

ARGOCD_ -> CD_ and REDIS_ -> KV_ across 345 files, plus the 8 e2e/cmp
fixtures that assert the plugin env contract — those had to move with the
binary, which now emits CD_APP_NAME where they expected ARGOCD_APP_NAME.

Left alone deliberately, because renaming them would be wrong:
- util/helm/testdata/redis/ and gitops-engine/.../statefulset*.yaml are
  fixtures for a THIRD-PARTY chart named redis, not our config
- util/kustomize/testdata/ likewise
- generated.proto regenerates from types.go, which is already clean

go build ./... exit 0.

LOCKSTEP: the live StatefulSet sets 47 ARGOCD_* names the binary no longer
reads. universe 4a5375735 carries the matching manifest change; they deploy
together or the controller falls back to defaults.

Co-authored-by: Hanzo Dev <[email protected]>
2026-07-28 15:55:46 -07:00

16 lines
661 B
Bash
Executable File

#!/usr/bin/env bash
# CD_E2E_DIR can be set to customize the e2e test data directory on the host
# This is useful on macOS where Docker doesn't share /tmp with the host
# The host directory is mounted to /tmp/argo-e2e inside the container
CD_E2E_DIR="${CD_E2E_DIR:-/tmp/argo-e2e}"
docker run --name e2e-git --rm -i \
-p 2222:2222 -p 9080:9080 -p 9443:9443 -p 9444:9444 -p 9445:9445 \
-w /go/src/github.com/argoproj/argo-cd \
-v /tmp:/tmp \
-v "$CD_E2E_DIR":/tmp/argo-e2e \
-v "$(pwd)":/go/src/github.com/argoproj/argo-cd \
docker.io/argoproj/argo-cd-ci-builder:v1.0.0 \
bash -c "goreman -f ./test/fixture/testrepos/Procfile start"