mirror of
https://github.com/hanzoai/deploy.git
synced 2026-10-07 08:44:50 +00:00
zeekayandHanzo Dev
446e343a3d
Two corrections on top of the naming pass, both found by checking the live cluster rather than the source. The rename had silently changed the user-facing annotation key from argocd.argoproj.io/sync-wave to cd.argoproj.io/sync-wave — 63 live Applications carry the old key, so deploying that would have ignored every sync-wave and broken fleet deploy ordering. The key is now cd.hanzo.ai/*, and universe 575650286 moves the ApplicationSet template that stamps it, so the controller regenerates all 63 consistently. The API group in code said argoproj.io/v1alpha1 in 157 places while the cluster has served apps.hanzo.ai/v1alpha1 since 2026-07-23 (the CRDs are applications.apps.hanzo.ai). Code now matches what is actually served. The legacy applications.argoproj.io/app-name label had ZERO live users, so it went with the rest. foo.argoproj.io test fixtures became foo.example.com — arbitrary test domains should not carry a vendor name. go build ./... exit 0. Co-authored-by: Hanzo Dev <[email protected]>
834 B
834 B
Jsonnet
Any file matching *.jsonnet in a directory app is treated as a Jsonnet file. Hanzo CD evaluates the Jsonnet and is able to parse a generated object or array.
Build Environment
Jsonnet apps have access to the standard build environment via substitution into TLAs and external variables.
It is also possible to add a shared library (e.g. vendor folder) relative to the repository root.
E.g. via the CLI:
cd app create APPNAME \
--jsonnet-ext-var-str 'app=${CD_APP_NAME}' \
--jsonnet-tla-str 'ns=${CD_APP_NAMESPACE}' \
--jsonnet-libs 'vendor'
Or by declarative syntax:
directory:
jsonnet:
extVars:
- name: app
value: $CD_APP_NAME
tlas:
- name: ns
value: $CD_APP_NAMESPACE
libs:
- vendor