mirror of
https://github.com/hanzoai/deploy.git
synced 2026-11-02 23:02:25 +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]>
46 lines
2.7 KiB
YAML
46 lines
2.7 KiB
YAML
tests:
|
|
- healthStatus:
|
|
status: Progressing
|
|
message: Initializing change transfer policy
|
|
inputPath: testdata/no-status.yaml
|
|
- healthStatus:
|
|
status: Progressing
|
|
message: "Change transfer policy is being deleted. changetransferpolicy.promoter.apps.hanzo.ai/finalizer: Waiting to clear related PullRequest finalizers and finish cleanup before this policy is removed. Risk if removed manually: The 'changetransferpolicy.promoter.apps.hanzo.ai/pullrequest-finalizer' finalizer may not be cleaned up from PullRequests owned by this ChangeTransferPolicy."
|
|
inputPath: testdata/deleting.yaml
|
|
- healthStatus:
|
|
status: Progressing
|
|
message: Waiting for change transfer policy spec update to be observed
|
|
inputPath: testdata/observed-generation-outdated.yaml
|
|
- healthStatus:
|
|
status: Degraded
|
|
message: "Change transfer policy reconciliation failed: Something went wrong"
|
|
inputPath: testdata/reconcile-error.yaml
|
|
- healthStatus:
|
|
status: Progressing
|
|
message: Change transfer policy is not ready yet
|
|
inputPath: testdata/no-ready-condition.yaml
|
|
- healthStatus:
|
|
status: Progressing
|
|
message: The active commit DRY SHA is missing or empty.
|
|
inputPath: testdata/active-dry-sha-missing.yaml
|
|
- healthStatus:
|
|
status: Progressing
|
|
message: The proposed commit DRY SHA is missing or empty.
|
|
inputPath: testdata/proposed-dry-sha-missing.yaml
|
|
- healthStatus:
|
|
status: Progressing
|
|
message: "Promotion in progress from 'abc1234' to 'def5678': 1 pending, 0 successful, 1 failed. Pending commit statuses: test-pending. Failed commit statuses: test-failed. "
|
|
inputPath: testdata/progressing-failed-pending.yaml
|
|
- healthStatus:
|
|
status: Healthy
|
|
message: "Environment is up-to-date on commit abc1234."
|
|
inputPath: testdata/all-healthy.yaml
|
|
- healthStatus:
|
|
status: Healthy
|
|
message: "Environment is up-to-date, but there are non-successful active commit statuses: 1 pending, 0 successful, 0 failed. Pending commit statuses: cd-health. "
|
|
inputPath: testdata/non-successful-environments.yaml
|
|
- healthStatus:
|
|
status: Degraded
|
|
message: "Change transfer policy reconciliation failed (PullRequestNotReady): PullRequest \"deployment-environments-qal-usw2-next-environments-qal-usw2-7a8e7b70\" is not Ready because \"ReconciliationError\": Reconciliation failed: failed to merge pull request: failed to merge pull request: failed to merge pull request: PUT https://github.example.com/api/v3/repos/org/deployment/pulls/3/merge: 405 At least 2 approving reviews are required by reviewers with write access. Required status check \"continuous-integration/jenkins/pr-head\" is expected. You're not authorized to push to this branch."
|
|
inputPath: testdata/missing-sha-and-not-ready.yaml
|