mirror of
https://github.com/hanzoai/deploy.git
synced 2026-10-30 14:56:59 +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]>
26 lines
667 B
YAML
26 lines
667 B
YAML
apiVersion: grafana.integreatly.org/v1beta1
|
|
kind: GrafanaFolder
|
|
metadata:
|
|
annotations:
|
|
cd.hanzo.ai/installation-id: cd.com
|
|
cd.hanzo.ai/tracking-id: >-
|
|
foo:grafana.integreatly.org/GrafanaFolder:grafana-operator/bar
|
|
creationTimestamp: '2025-03-26T14:50:23Z'
|
|
finalizers:
|
|
- operator.grafana.com/finalizer
|
|
generation: 1
|
|
labels:
|
|
cd.hanzo.ai/instance: foo
|
|
name: bar
|
|
namespace: grafana-operator
|
|
resourceVersion: '185974148'
|
|
uid: 226a9af3-4a5d-4ebb-9705-ddfec0f6db47
|
|
spec:
|
|
allowCrossNamespaceImport: false
|
|
instanceSelector:
|
|
matchLabels:
|
|
dashboards: grafana
|
|
parentFolderRef: baz
|
|
resyncPeriod: 10m0s
|
|
title: Bar-Folder
|