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]>
30 lines
1.2 KiB
YAML
30 lines
1.2 KiB
YAML
tests:
|
|
- healthStatus:
|
|
status: Progressing
|
|
message: Initializing cluster SCM provider
|
|
inputPath: testdata/no-status.yaml
|
|
- healthStatus:
|
|
status: Progressing
|
|
message: 'ClusterScmProvider is being deleted. clusterscmprovider.promoter.apps.hanzo.ai/finalizer: Waiting until no GitRepository still references this cluster-wide SCM provider. Risk if removed manually: GitRepository objects can reference a provider that no longer exists.'
|
|
inputPath: testdata/deleting.yaml
|
|
- healthStatus:
|
|
status: Progressing
|
|
message: Waiting for ClusterScmProvider spec update to be observed
|
|
inputPath: testdata/observed-generation-outdated.yaml
|
|
- healthStatus:
|
|
status: Degraded
|
|
message: "Cluster SCM provider validation failed: Reconciliation failed: invalid credentials"
|
|
inputPath: testdata/reconcile-error.yaml
|
|
- healthStatus:
|
|
status: Progressing
|
|
message: ClusterScmProvider Ready condition is missing
|
|
inputPath: testdata/no-ready-condition.yaml
|
|
- healthStatus:
|
|
status: Progressing
|
|
message: "Cluster SCM provider readiness unknown (ValidationPending): Probing SCM endpoint"
|
|
inputPath: testdata/ready-unknown.yaml
|
|
- healthStatus:
|
|
status: Healthy
|
|
message: Cluster SCM provider is ready
|
|
inputPath: testdata/healthy.yaml
|