mirror of
https://github.com/hanzoai/deploy.git
synced 2026-10-07 08:44:50 +00:00
zeekayandHanzo Dev
1ab6e799c1
go.mod still declared `module github.com/hanzoai/deploy` after the repo was renamed. A Go module path is not cosmetic — it is the resolvable location. So `go get github.com/hanzoai/cd` could not work, and anything importing this module had to spell a name that no longer exists at that address. The build log of v3.6.0 is where it surfaced: the compiler was still emitting github.com/hanzoai/deploy/cmd/cd/commands. 3541 import paths across 690 .go, 19 .proto, 4 .yaml, 3 .sh, 2 .mod, Procfile and Makefile. Plus the 62 ghcr.io/hanzoai/deploy image references, moved to ghcr.io/hanzoai/cd to match hanzo.yml's build target — a distinct string from the module path, replaced separately so neither could clobber the other. go mod tidy clean, CGO_ENABLED=0 GOOS=linux GOARCH=amd64 go build ./... clean. Co-authored-by: Hanzo Dev <[email protected]>
45 lines
1.9 KiB
YAML
45 lines
1.9 KiB
YAML
# Canonical CI/CD config for hanzoai/cd ("Hanzo CD") — read by both the
|
|
# hanzoai/ci reusable workflow (.github/workflows/cicd.yml) and
|
|
# platform.hanzo.ai.
|
|
#
|
|
# One image: the root multi-stage Dockerfile builds the UI plus every cd-*
|
|
# binary (cd, cd-server, cd-repo-server, cd-application-controller,
|
|
# cd-applicationset-controller, cd-commit-server, cd-cmp-server, cd-dex,
|
|
# cd-git-ask-pass, cd-k8s-auth) into it.
|
|
#
|
|
# The image is ghcr.io/hanzoai/cd — matching the repo, the binaries, the
|
|
# apps.hanzo.ai API group and the cd.hanzo.ai UI. It read ghcr.io/hanzoai/cd
|
|
# until now, the name from before the repo was renamed, and this file was the
|
|
# last place that name survived: universe's infra/k8s/hanzo-cd/README.md has
|
|
# documented the engine as ghcr.io/hanzoai/cd throughout. A build target that
|
|
# outlives the name of the thing it builds is how the two quietly stop meaning
|
|
# each other.
|
|
images:
|
|
- name: cd
|
|
context: .
|
|
dockerfile: Dockerfile
|
|
repo: ghcr.io/hanzoai/cd
|
|
|
|
# Light gate: the multi-stage Dockerfile build is slow (UI + full Go build),
|
|
# so `go-build` fails a broken PR fast, before waiting on the full image.
|
|
test:
|
|
- name: go-build
|
|
run: CGO_ENABLED=0 go build ./...
|
|
|
|
# BUILD-ONLY, deliberately: no `deploy:` block. The live `hanzo-cd` namespace
|
|
# reconciles the whole Hanzo fleet — Hanzo CD IS the delivery mechanism for
|
|
# everything else — so a cutover is a separately-greenlit action, never an
|
|
# auto-deploy on merge. See universe: infra/k8s/hanzo-cd/ for the prepared swap.
|
|
# (Same controlled build-only-first pattern as hanzoai/cms.)
|
|
#
|
|
# The standing consequence, stated so it is a choice and not a surprise: nothing
|
|
# here rolls a new image out. The running engine changes only when someone
|
|
# applies it.
|
|
|
|
# KMS (kms.hanzo.ai, Universal Auth) supplies the GHCR push token at run time.
|
|
# Only KMS_CLIENT_ID/KMS_CLIENT_SECRET live in GitHub; everything else is
|
|
# fetched here.
|
|
kms:
|
|
path: /deploy
|
|
environment: prod
|