Files
zeekayandHanzo Dev 84ee9fa0ce cd: kill the argo naming — binaries, packages, identifiers
Every command is cd-*: cd, cd-server, cd-repo-server,
cd-application-controller, cd-applicationset-controller, cd-cmp-server,
cd-commit-server, cd-dex, cd-git-ask-pass, cd-k8s-auth, cd-notification.
util/argo is util/cd; util/notification/argocd is util/notification/cd.

Preserved deliberately: github.com/argoproj/argocd-example-apps is an
EXTERNAL repo used as an e2e fixture, and notifications-engine + pkg/v2 are
real dependencies. Renaming a URL we do not own would break the tests.

Two bugs I made and caught, both from a careless sed:
- s/argo/cd/g turned 'argocd' into 'cdcd' in two directory names
- renaming the package declaration left every call site saying argo.X

go build ./... exit 0.

Co-authored-by: Hanzo Dev <[email protected]>
2026-07-28 16:00:25 -07:00

22 lines
781 B
YAML

tests:
- healthStatus:
status: Healthy
message: ApplicationSet up to date
inputPath: testdata/healthyApplicationSet.yaml
- healthStatus:
status: Degraded
message: found less than two generators, Merge requires two or more
inputPath: testdata/errorApplicationSetWithStatusMessage.yaml
- healthStatus:
status: Progressing
message: Waiting for the status to be reported
inputPath: testdata/noStatusApplicationSet.yaml
- healthStatus:
status: Degraded
message: could not create application
inputPath: testdata/resourceNotUpdatedApplicationSet.yaml
- healthStatus:
status: Progressing
message: ApplicationSet is performing rollout of step 1
inputPath: testdata/progressiveSyncApplicationSet.yaml