Files
zooqueen 5034da630c drop GOPRIVATE from the test gate — this graph is entirely public
GOPRIVATE means "bypass the proxy AND the checksum database", and bypassing the
proxy is what sends the toolchain to github.com needing a credential. Every
module this repo requires — hanzoai/goexif, hanzoai/s3 and hanzoai/s3-csi
included — is served by the public proxy, measured across the whole graph.

So this removes a credential dependency and gains the checksum verification it
was skipping.
2026-08-20 00:48:43 -07:00

33 lines
1.3 KiB
YAML

# Canonical CI config for hanzoai/s3-csi — read by the hanzoai/ci reusable
# (.hanzo/workflows/cicd.yml) and by platform.hanzo.ai. One file, one place.
#
# This replaces three GitHub workflows that each built THE SAME two images
# (dev.yaml, release.yaml, versioned_release.yaml). Three builders on one commit
# is three chances to publish something nobody asked for; the images: block below
# is the single declaration of what this repo produces.
images:
- name: s3-csi
context: .
dockerfile: cmd/s3-csi-driver/Dockerfile
repo: ghcr.io/hanzoai/s3-csi
- name: s3-mount
context: .
dockerfile: cmd/s3-mount/Dockerfile
repo: ghcr.io/hanzoai/s3-mount
test:
- name: go
# The driver's storage path talks ZAP to the filer; keep it building and its
# unit tests honest before anything is published.
run: |
set -e
# No GOPRIVATE. It means "bypass the proxy AND the checksum database", and
# bypassing the proxy is what sends the toolchain to github.com needing a
# credential. Every module this repo requires — hanzoai/goexif, hanzoai/s3,
# hanzoai/s3-csi included — is served by the public proxy, so dropping it
# removes a credential and gains checksum-log verification.
export GOWORK=off
go vet ./...
go test ./...