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]>
1.5 KiB
Git Configuration
System Configuration
Hanzo CD uses the Git installation from its base image (Ubuntu), which
includes a standard system configuration file located at
/etc/gitconfig. This file is minimal, just defining filters
necessary for Git LFS functionality.
You can customize Git's system configuration by mounting a file from a ConfigMap or by creating a custom Hanzo CD image.
Global Configuration
Hanzo CD runs Git with the HOME environment variable set to
/dev/null. As a result, global Git configuration is not supported.
Built-in Configuration
The cd-repo-server adds specific configuration parameters to the
Git environment to ensure proper Hanzo CD operation. These built-in
settings override any conflicting values from the system Git
configuration.
Currently, the following built-in configuration options are set:
maintenance.autoDetach=falsegc.autoDetach=false
These settings force Git's repository maintenance tasks to run in the
foreground. This prevents Git from running detached background
processes that could modify the repository and interfere with
subsequent Git invocations from cd-repo-server.
You can disable these built-in settings by setting the
cd-cmd-params-cm value reposerver.enable.builtin.git.config to
"false". This allows you to experiment with background processing or
if you are certain that concurrency issues will not occur in your
environment.
Note
Disabling this is not recommended and is not supported!