Files
deploy/test/e2e/serverside_diff_test.go
41536738c8 refactor(cd): hard-fork - rename CRD API group argoproj.io -> deploy.hanzo.ai (#1)
* feat(api): hard-fork CRD API group argoproj.io -> deploy.hanzo.ai

Hanzo CD hard-fork, phase 1.1. Single source of truth is
pkg/apis/application/register.go's Group constant (Application/AppProject/
ApplicationSet all derive their FullName from it); every other Go call-site
that hardcoded the literal group string is updated to match: the 3 generated
informer GVRs, the app-of-apps nested-Application detector in types.go, the
resource-tree Application-kind cache populator, the 3 NotFound error
constructors in server/application, and the applicationset-controller's
leader-election Lease name/ID (kept in lockstep across Go source + RBAC
resourceNames, or leader election would get RBAC-denied on startup).

CRD YAMLs (application/appproject/applicationset) and every RBAC apiGroups
rule that actually governs our 3 CRDs are repointed to deploy.hanzo.ai, across
both manifests/base/* (namespaced Roles) and manifests/cluster-rbac/* (cluster
scope). Two adjacent things that share the "argoproj.io" string but are NOT
ours are deliberately left untouched: gitops-engine's health-check dispatch
for Argo Workflows' `Workflow` kind, and argocd-server-clusterrole's second
apiGroups block granting read on Argo Workflows' `workflows` resource — both
belong to a separate, unrelated Argoproj-family project we are not forking.

Also untouched, per explicit scope: annotation/label keys (argocd.argoproj.io/*)
and finalizers (*.argoproj.io) that track already-applied live resources, and
argocd-cm.yaml's resource.customizations.ignoreResourceUpdates keys (a narrow
app-of-apps diffing nicety, not build- or RBAC-relevant).

CGO_ENABLED=0 go build ./... verified green.

* ci: wire canonical hanzo.yml + cicd.yml (Hanzo CD image build)

Phase 1.3. Follows the same one-way pattern every hanzo/lux/zoo repo uses:
hanzo.yml declares the image (root Dockerfile -> ghcr.io/hanzoai/deploy) and a
fast go-build sanity test (the multi-stage Dockerfile build is the slow, real
gate); cicd.yml is the ~10-line trigger shim importing hanzoai/ci's reusable
build workflow on the arc pool, secrets from KMS only.

No `deploy:` block yet, matching the hanzoai/cms build-only-first-cutover
pattern: this repo's own live hanzo-cd namespace runs the whole Hanzo fleet's
GitOps, so the prod image/CRD swap is a deliberate separate action (see the
[HELD] universe PR), never an automatic rollout on merge. Every PR/push still
builds and pushes an immutable ghcr.io/hanzoai/deploy:sha-<7>-amd64 image.

* feat(ui): rebrand Argo CD -> Hanzo CD (title, favicon, logo, sidebar)

Phase 1.2. User-facing "Argo CD"/"ArgoCD" text replaced with "Hanzo CD"
across the login page, help modal, settings screens, version-info panel,
sync-options warning, fullscreen-logs title, app.tsx page titles, and
index.html's <title>/noscript text (dropped the now-wrong upstream CLI
doc link rather than invent a hanzo.ai URL that doesn't exist).

Logo/favicon assets replaced with the canonical Hanzo mark (never
hand-drawn, copied from ~/work/hanzo/logo/dist): the two real usages of
Argo's logo collapse onto one Hanzo glyph (mono + white variants) at the
same 5 call sites (login icon + footer, login.scss $logoPath/
$logoNegativePath, sidebar text-logo), preserving the existing CSS
invert() filters so both the light login panel and dark sidebar still
render correctly. Old argologo.svg/argo_o.svg/argo.png deleted (no
longer referenced). favicon-{16x16,32x32}.png added at
ui/src/assets/favicon/ (index.html's links to that path were previously
dead - the directory didn't exist in this checkout). package.json name
argo-cd-ui -> hanzo-cd-ui.

Left alone, deliberately: the two Kubernetes resource-kind icon sets
under ui/src/assets/images/resources/ (unrelated to branding), and
upstream doc/project links (argoproj.io, argo-cd.readthedocs.io) since
we have no equivalent hanzo.ai docs to point to yet - except the login
footer logo's outbound link, which now points to hanzo.ai instead of
argoproj.io (a Hanzo-branded mark linking to the upstream project it
was forked from read as an obvious leftover).

* feat(module): rename Go module github.com/argoproj/argo-cd/v3 -> github.com/hanzoai/deploy

Phase 2. No version suffix on the new path (org policy: never publish our
own Go modules above v1.x.x / with a v2+ suffix) — this fork starts a fresh
v0/v1 module identity rather than carrying the v3 the upstream fork point
had reached.

Mechanical, symmetric rewrite: 704 .go files (import statements only; two
disjoint substitutions applied specific-first so the nested gitops-engine
module path never double-matches), plus go.mod (module line, the
gitops-engine require+replace pair, version reset to v0.0.0-... since a
suffix-less path can't carry a v3 semver), gitops-engine/go.mod, Makefile
(ldflags PACKAGE + 2 TEST_MODULE filters), .golangci.yaml, .goreleaser.yaml,
.mockery.yaml (+ gitops-engine's), Procfile, the codegen/proto generation
scripts (hack/generate-proto.sh, update-codegen.sh, update-openapi.sh), and
20 .proto files' go_package options. Also one OpenTelemetry tracer name
string in gitops-engine/pkg/sync/sync_context.go (a cosmestic label, not an
import, but worth keeping consistent).

CGO_ENABLED=0 go build ./... verified green for both the root module and
the nested gitops-engine module; go vet clean on both; go mod tidy run
(network available) to reconcile go.sum, dependency set unchanged.

Left alone, deliberately: doc-only mentions (docs/snyk/*.html scan reports,
gitops-engine/README.md), a comment-only reference in
.github/workflows/release.yaml, and one Renovate bot config line — none are
build- or codegen-load-bearing. Also left alone: comments citing upstream
GitHub issue URLs (github.com/argoproj/argo-cd/issues/NNNNN) and a handful
of test fixtures using "https://github.com/argoproj/argo-cd.git" as a
representative example repo URL — both are accurate historical/test-data
references, not stale self-references.

---------

Co-authored-by: Hanzo Dev <[email protected]>
2026-07-29 18:27:58 -07:00

140 lines
4.7 KiB
Go

package e2e
import (
"encoding/base64"
"encoding/json"
"fmt"
"testing"
"github.com/stretchr/testify/assert"
"github.com/stretchr/testify/require"
metav1 "k8s.io/apimachinery/pkg/apis/meta/v1"
"k8s.io/apimachinery/pkg/apis/meta/v1/unstructured"
"k8s.io/apimachinery/pkg/types"
applicationpkg "github.com/hanzoai/deploy/pkg/apiclient/application"
. "github.com/hanzoai/deploy/pkg/apis/application/v1alpha1"
. "github.com/hanzoai/deploy/test/e2e/fixture"
. "github.com/hanzoai/deploy/test/e2e/fixture/app"
utilio "github.com/hanzoai/deploy/util/io"
)
// TestServerSideDiffMasksSecretData is a regression test for a CVE where the
// ServerSideDiff endpoint returned plaintext Kubernetes Secret values from etcd.
func TestServerSideDiffMasksSecretData(t *testing.T) {
closer, client, err := ArgoCDClientset.NewApplicationClient()
require.NoError(t, err)
defer utilio.Close(closer)
Given(t).
Path("secrets").
When().
CreateApp().
Sync().
Then().
Expect(SyncStatusIs(SyncStatusCodeSynced)).
And(func(app *Application) {
ns := app.Spec.Destination.Namespace
// Establish a second SSA field manager owning the secret's data field.
// Without a second manager, argocd-controller is the sole owner and the
// SSA dry-run garbage-collects the data fields (since the target manifest
// omits them). A second manager retains ownership, so the real values
// survive in the dry-run response — the exact condition required for the
// CVE to be exploitable.
secretPatch := fmt.Sprintf(
`{"apiVersion":"v1","kind":"Secret","metadata":{"name":"test-secret","namespace":%q},"data":{"username":%q}}`,
ns,
base64.StdEncoding.EncodeToString([]byte("test-username")),
)
_, err := KubeClientset.CoreV1().Secrets(ns).Patch(
t.Context(),
"test-secret",
types.ApplyPatchType,
[]byte(secretPatch),
metav1.PatchOptions{FieldManager: "test-manager"},
)
require.NoError(t, err)
// Annotate the app with IncludeMutationWebhook=true — the condition that
// bypasses removeWebhookMutation() and exposed real etcd values in the response.
_, err = RunCli("app", "patch", app.Name,
"--patch", `{"metadata":{"annotations":{"argocd.argoproj.io/compare-options":"IncludeMutationWebhook=true"}}}`,
"--type", "merge",
)
require.NoError(t, err)
// Fetch the masked live state as ArgoCD sees it.
// This is the same data an attacker would read from managed-resources
// before crafting the ServerSideDiff request.
resources, err := client.ManagedResources(t.Context(), &applicationpkg.ResourcesQuery{
ApplicationName: &app.Name,
})
require.NoError(t, err)
var secretLiveState string
for _, r := range resources.Items {
if r.Kind == "Secret" && r.Name == "test-secret" {
secretLiveState = r.LiveState
break
}
}
require.NotEmpty(t, secretLiveState, "test-secret not found in managed resources")
// Build a minimal target manifest with no data field — exactly what the
// exploit sends to force the SSA dry-run to return data owned by the
// second field manager (i.e., real etcd values).
target, err := json.Marshal(map[string]any{
"apiVersion": "v1",
"kind": "Secret",
"metadata": map[string]any{"name": "test-secret", "namespace": ns},
"type": "Opaque",
})
require.NoError(t, err)
resp, err := client.ServerSideDiff(t.Context(), &applicationpkg.ApplicationServerSideDiffQuery{
AppName: &app.Name,
Project: &app.Spec.Project,
LiveResources: []*ResourceDiff{{
Kind: "Secret",
Namespace: ns,
Name: "test-secret",
LiveState: secretLiveState,
Modified: true,
}},
TargetManifests: []string{string(target)},
})
require.NoError(t, err)
require.NotEmpty(t, resp.Items, "expected at least one diff item in response")
for _, item := range resp.Items {
if item.Kind != "Secret" {
continue
}
assertServerSideDiffSecretMasked(t, item.TargetState, "targetState")
assertServerSideDiffSecretMasked(t, item.LiveState, "liveState")
}
})
}
// assertServerSideDiffSecretMasked verifies that every value in the data field of the
// given secret JSON manifest consists only of '+' characters (ArgoCD's masking format).
func assertServerSideDiffSecretMasked(t *testing.T, manifest, field string) {
t.Helper()
if manifest == "" || manifest == "null" {
return
}
obj := &unstructured.Unstructured{}
require.NoError(t, obj.UnmarshalJSON([]byte(manifest)), "failed to parse %s as JSON", field)
data, hasData, err := unstructured.NestedStringMap(obj.Object, "data")
require.NoError(t, err)
if !hasData || len(data) == 0 {
return
}
for k, v := range data {
assert.Regexp(t, `^\++$`, v,
"%s: secret key %q must be masked with '+' characters, got %q", field, k, v)
}
}