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]>
23 lines
433 B
YAML
23 lines
433 B
YAML
apiVersion: v1
|
|
kind: ConfigMap
|
|
metadata:
|
|
name: test-configmap
|
|
namespace: default
|
|
uid: 12345678-1234-1234-1234-123456789012
|
|
resourceVersion: "1000"
|
|
managedFields:
|
|
- manager: cd-controller
|
|
operation: Apply
|
|
apiVersion: v1
|
|
time: "2024-01-01T00:00:00Z"
|
|
fieldsType: FieldsV1
|
|
fieldsV1:
|
|
f:data:
|
|
f:key1: {}
|
|
f:key2: {}
|
|
f:key3: {}
|
|
data:
|
|
key1: value1
|
|
key2: value2
|
|
key3: value3
|