Validate app, parts, and registry schemas on deserialization
Dependencies in a ksonnet application are installed from collections of
packages called registries. In order to be precise about which packages
an app depends on, and where they are from, we have an API that
specifies each of these nouns.
Unfortunately, we never hooked up code to verify the versions of these
specifications as we deserialize them.
This commit will correct that.
Signed-off-by:
Alex Clemmer <clemmer.alexander@gmail.com>
Showing
- metadata/app/schema.go 31 additions, 0 deletionsmetadata/app/schema.go
- metadata/app/schema_test.go 44 additions, 0 deletionsmetadata/app/schema_test.go
- metadata/manager.go 2 additions, 4 deletionsmetadata/manager.go
- metadata/parts/schema.go 35 additions, 1 deletionmetadata/parts/schema.go
- metadata/parts/schema_test.go 64 additions, 0 deletionsmetadata/parts/schema_test.go
- metadata/registry.go 4 additions, 7 deletionsmetadata/registry.go
- metadata/registry/schema.go 40 additions, 1 deletionmetadata/registry/schema.go
- metadata/registry/schema_test.go 64 additions, 0 deletionsmetadata/registry/schema_test.go
- metadata/registry_managers.go 6 additions, 10 deletionsmetadata/registry_managers.go
- metadata/registry_test.go 1 addition, 1 deletionmetadata/registry_test.go
- prototype/interface.go 4 additions, 0 deletionsprototype/interface.go
- prototype/prototype_test.go 47 additions, 3 deletionsprototype/prototype_test.go
- prototype/specification.go 19 additions, 0 deletionsprototype/specification.go
Please register or sign in to comment