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]>
* docs: update wording in diffing.md
The wording in "If you have a slash / in your pointer path, you can use the ~1 character" is inaccurate. The ~1 character is mandatory if you have a slash.
Signed-off-by: Daniel R. Dagfinrud <[email protected]>
* docs: update wording in docs/user-guide/diffing.md
Co-authored-by: Blake Pettersson <[email protected]>
Signed-off-by: Daniel R. Dagfinrud <[email protected]>
---------
Signed-off-by: Daniel R. Dagfinrud <[email protected]>
Co-authored-by: Blake Pettersson <[email protected]>
So that this can be used for custom resources. The motivation for this
is issue #6008: with this change one should be able to use the known
type to ensure equal durations don't present a diff, e,g. via adding to
`argocd-cm`:
data:
resource.customizations.knownTypeFields.cert-manager.io_Certificate: |
- field: spec.duration
type: meta/v1/Duration
This change is based on 0a515b39b7, though
I've included the API version in the type path to be consistent with the
generated type (i.e. `meta/v1/Duration` and not `meta/Duration`).
For documentation I've just manually listed the extra types that aren't
auto-generated, though this requires having to keep this list and the
code in-sync but this is probably not a big issue since the number of
extra types is not frequently changed.
In the tests I've used `require.*` methods since I find this simpler
than `if !assert.Blah(...) { return }` which the other tests in this
file are using.
Signed-off-by: Matthew Hughes <[email protected]>
Reordering `spec.metrics` will fix an OutOfSync state due to the HPA
controller reordering this array. The previously referenced
`spec.replicas` field doesn't exist within any known version of the
`HorizontalPodAutoscaler` (autoscaling/v1, autoscaling/v2beta1, or
autoscaling/v2beta2)
zeekayandHanzo Dev