mirror of
https://github.com/hanzoai/cd.git
synced 2026-10-30 14:56:45 +00:00
zeekay
0d4229f4af
The release Dockerfile's shipped binaries and symlinks were already hanzocd-*, but the build stages feeding them weren't: stage names (argocd-base/-ui/-build), the in-container build user/group/home (argocd, uid 999 — renamed in place, same uid so no ownership fallout), and the GOPATH-style build WORKDIR (.../argoproj/argo-cd) all still carried the pre-fork name. Same in Dockerfile.dev, hack/Dockerfile.dev-tools, and ui/scripts/build_docker.sh. The Makefile and both Procfiles (root + test/container) had the matching half of this: CD_BINARY_NAME values that don't match any case in cmd/main.go's dispatch switch (all hanzocd-*), a --argocd-repo-server flag no command registers (the real one is --cd-repo-server), a `kubectl get secret argocd-redis` that can never succeed (the Secret the redis manifest actually mounts is hanzocd-redis), `kubectl create ns argocd`/argocd-e2e(-external(-2)) that don't match the namespaces test/e2e/fixture actually uses (cd/cd-e2e/cd-e2e-external(-2)), a TEST_MODULE filter matching the pre-fork gitops-engine import path only, and IMAGE_REGISTRY/IMAGE_NAMESPACE/IMAGE_REPOSITORY defaults that silently point an override-less `make image` at quay.io/argoproj/argocd instead of ghcr.io/hanzoai/cd. Also folded three different stale /tmp scratch-dir spellings (argocd-local, argocd-e2e-env, argo-e2e) into the one each already-correct sibling file used, so Procfile/Makefile/reaper.sh/ start-git.sh/fixture.go/nginx.conf all agree again — see LLM.md for the full map, it's not worth re-deriving twice. Deleted hack/bump-major-version.sh: it bumps a github.com/.../vN import-path suffix, a scheme this module has never used (no /v2, /v3 — we don't bump Go majors) and nothing else in the repo references it.