The previous commit in this PR regenerated schema and CRD artefacts
using a local 'dev' build of cozyvalues-gen, which sorts
properties alphabetically. CI installs the pinned upstream release
(v1.3.0), which preserves values.yaml source order, so the committed
outputs diverged from what CI regenerates and pre-commit failed with
exit code 123.
Re-ran 'make generate' locally with the release binary from
https://github.com/cozystack/cozyvalues-gen/releases/tag/v1.3.0 to
produce the same output the CI pipeline expects.
Files refreshed:
- api/apps/v1alpha1/tenant/types.go — field order reverted to
values.yaml source order (host, etcd, monitoring, ingress, gateway,
seaweedfs, schedulingClass, resourceQuotas).
- packages/apps/tenant/values.schema.json — same reordering.
- packages/system/tenant-rd/cozyrds/tenant.yaml — regenerated from
the refreshed schema, gateway bool field now properly sorted.
- packages/extra/gateway/values.schema.json — regenerated for the
same reason; gateway package itself has only one field so the diff
is cosmetic, but keeps the pipeline clean.
Assisted-By: Claude <noreply@anthropic.com>
Signed-off-by: Aleksei Sviridkin <f@lex.la>
8afa6601c9