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]>
* added an example of downloading the latest stable version
Signed-off-by: Christian Hernandez <[email protected]>
* Update docs/cli_installation.md
Co-authored-by: Ishita Sequeira <[email protected]>
Signed-off-by: Christian Hernandez <[email protected]>
---------
Signed-off-by: Christian Hernandez <[email protected]>
Signed-off-by: Christian Hernandez <[email protected]>
Co-authored-by: Ishita Sequeira <[email protected]>
Added CLI command for adding Argo CD in environmental variables PATH in Windows
When Argo CD Is installed using PowerShell in Windows it is required to add an environment variable for getting started
this command can be readily used to add it and start using ```argocd``` command.
Signed-off-by: ajinkyak423 <[email protected]>
Co-authored-by: Michael Crenshaw <[email protected]>
zeekayandHanzo Dev