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]>
26 lines
693 B
YAML
26 lines
693 B
YAML
apiVersion: tower.ansible.com/v1alpha1
|
|
kind: AnsibleJob
|
|
metadata:
|
|
annotations:
|
|
cd.hanzo.ai/hook: PreSync
|
|
creationTimestamp: "2023-06-27T20:22:22Z"
|
|
generateName: prehook-test-
|
|
generation: 1
|
|
labels:
|
|
app.kubernetes.io/instance: ansible-hooks
|
|
tower_job_id: "1"
|
|
name: prehook-test-dfcff01-presync-1687897341
|
|
namespace: cd
|
|
resourceVersion: "6536518"
|
|
uid: 09fa0d39-a170-4c37-a3b0-6e140e029868
|
|
spec:
|
|
job_template_name: Demo Job Template
|
|
tower_auth_secret: toweraccess
|
|
status:
|
|
ansibleJobResult:
|
|
changed: true
|
|
failed: false
|
|
started: "2023-06-27T20:22:34.906399Z"
|
|
status: waiting
|
|
url: https://cd.test.ansiblejob.custom.health.com/#/jobs/playbook/1
|