mirror of
https://github.com/luxfi/kms.git
synced 2026-07-26 23:59:24 +00:00
zeekayandHanzo Dev
525646f150
299b230 deleted this in favour of platform.hanzo.ai native builds (hanzo.yml).
The native plane does not serve yet — the platform Deployment is scaled to 0/0
and PLATFORM_BUILD_CALLBACK_TOKEN, the bearer POST /v1/runner requires, is in
neither cluster — so the cutover left kms the one repo in the fleet that could
not build at all, while every sibling kept building on Actions (luxfi/node has
19 active workflows, hanzoai/gateway 3, hanzoai/commerce 1).
The 422 that motivated the cutover, "Actions has been disabled for this user",
is account-scoped rather than repo-scoped: hanzo-dev gets it, zeekay does not.
Push-triggered runs separately stopped firing around 2026-07-24, so builds want
an explicit dispatch regardless.
hanzo.yml stays and now says plainly that it is intent, not the live path. Cut
over when the native plane serves, and fleet-wide rather than one repo at a time.
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
33 lines
1.5 KiB
YAML
33 lines
1.5 KiB
YAML
# Build is owned by platform.hanzo.ai, not GitHub Actions. Platform reads this
|
|
# file, schedules the image build onto the self-hosted arcd pools over the
|
|
# native long-poll fabric, and pushes to GHCR — no GitHub-Actions hop.
|
|
#
|
|
# STATUS: declaration of intent, NOT the live path. The build that actually runs
|
|
# today is .github/workflows/build-lux-kms.yml, restored after this file briefly
|
|
# replaced it — the native plane is not serving yet (the platform Deployment is
|
|
# scaled to 0/0 and PLATFORM_BUILD_CALLBACK_TOKEN, the bearer POST /v1/runner
|
|
# needs, is in neither cluster), so cutting over left kms unable to build at all.
|
|
#
|
|
# The 422 "Actions has been disabled for this user" that motivated the cutover is
|
|
# ACCOUNT-scoped, not repo-scoped: the hanzo-dev account gets it, the zeekay
|
|
# account dispatches fine. Push-triggered runs did stop firing around 2026-07-24,
|
|
# so builds need an explicit dispatch either way.
|
|
#
|
|
# Switch to this path when the native plane serves, and do it for the whole fleet
|
|
# at once — every sibling repo still builds on Actions.
|
|
#
|
|
# Schema: ~/work/hanzo/platform/docs/PLATFORM_CI.md §hanzo.yml.
|
|
build:
|
|
matrix:
|
|
- { os: linux, arch: amd64 }
|
|
dockerfile: ./Dockerfile
|
|
context: .
|
|
image: ghcr.io/luxfi/kms
|
|
tag-pattern: "{{git.branch}}"
|
|
push: true
|
|
dispatch: native
|
|
|
|
# No `deploy:` block. The kms Deployment in the hanzo namespace is kustomize-
|
|
# managed and carries no operator CR, so there is nothing here for the Service-CR
|
|
# rollout to target. Rolling the image stays a separate, explicit step.
|