Timofei Larkin 180030be72 fix(api): refuse only what a name declaration actually breaks ...

Three cases refused creates of a kind, or were documented as refused,
without the declaration being at fault.

A schema that is not a JSON object was reported as an invalid
x-cozystack-name, although such a schema has no declaration to blame,
and the spec schema's own loader already reports it. It now declares
nothing, so creates keep working and a kind with a legacy cap keeps it.

Any unknown key inside a declaration took the kind offline, so a
generator adding a title or an example would do the same. Keywords that
constrain nothing, the JSON Schema annotations and x- extensions, are
now ignored. A constraint keyword the server does not implement is still
refused, because accepting it would drop it silently.

The docs said a declaration no name satisfies is refused. That holds
for lengths only: a pattern is checked to compile, not to match
anything. The docs now say so.

The parser moves to pkg/apis/apps/validation so the API review gate can
reuse it rather than keep a copy of its rules.

Assisted-by: LLM
Signed-off-by: Timofei Larkin <lllamnyp@gmail.com>

2026-09-24 09:35:10 +03:00

..

nameschema.go

fix(api): refuse only what a name declaration actually breaks

2026-09-24 09:35:10 +03:00

validation_test.go

test(api): address review round 4 findings

2026-04-12 14:17:12 +03:00

validation.go

test(api): address review round 4 findings

2026-04-12 14:17:12 +03:00