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]>
865 B
865 B
Additional configuration methods
Additional configuration methods for configuring commands cd-server, cd-repo-server and cd-application-controller.
Synopsis
The commands can also be configured by setting the respective flag of the available options in cd-cmd-params-cm.yaml. Each component has a specific prefix associated with it.
cd-server --> server
cd-repo-server --> reposerver
cd-application-controller --> controller
The flags that do not have a prefix are shared across multiple components. One such flag is repo.server
The list of flags that are available can be found in cd-cmd-params-cm.yaml
Example
To set logformat of cd-application-controller, add below entry to the config map cd-cmd-params-cm.yaml.
data:
controller.log.format: "json"