mirror of https://github.com/hanzoai/deploy.git synced 2026-10-07 08:44:50 +00:00

Files

T

zeekayandHanzo Dev 446e343a3d cd: annotations are cd.hanzo.ai, API group is apps.hanzo.ai

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]>

2026-07-28 16:32:14 -07:00

2.6 KiB

Raw Permalink Blame History

Managing Dependencies

Notifications Engine (`github.com/argoproj/notifications-engine`)

Repository

notifications-engine

Pulling changes from `notifications-engine`

After your Notifications Engine PR has been merged, Hanzo CD needs to be updated to pull in the version of the notifications engine that contains your change. Here are the steps:

Retrieve the SHA hash for your commit. You will use this in the next step.
From the argo-cd folder, run the following command

go get github.com/argoproj/notifications-engine@<git-commit-sha>

If you get an error message invalid version: unknown revision then you got the wrong SHA hash
Run:

go mod tidy
The following files are changed:
- go.mod
- go.sum
If your notifications engine PR included docs changes, run make codegen or make codegen-local.
Create an Hanzo CD PR with a chore: type in its title for the above file changes.

Argo UI Components (`github.com/argoproj/argo-ui`)

Contributing to Hanzo CD UI

Hanzo CD, along with Argo Workflows, uses shared React components from Argo UI. Examples of some of these components include buttons, containers, form controls, and others. Although you can make changes to these files and run them locally, in order to have these changes added to the Hanzo CD repo, you will need to follow these steps.

Fork and clone the Argo UI repository.
cd into your argo-ui directory, and then run pnpm install.
Make your file changes.
Run pnpm start to start a storybook dev server and view the components in your browser. Make sure all your changes work as expected.
Use pnpm link to link Argo UI package to your Hanzo CD repository. (Commands below assume that argo-ui and argo-cd are both located within the same parent folder)
- cd argo-ui
- pnpm link
- cd ../argo-cd/ui
- pnpm link argo-ui
Once the argo-ui package has been successfully linked, test changes in your local development environment.
Commit changes and open a PR to Argo UI.
Once your PR has been merged in Argo UI, cd into your argo-cd/ui folder and run pnpm add git+https://github.com/argoproj/argo-ui.git. This will update the commit SHA in the ui/pnpm-lock.yaml file to use the latest master commit for argo-ui.
Submit changes to ui/pnpm-lock.yaml in a PR to Hanzo CD.

2.6 KiB Raw Permalink Blame History