a07bfe7dfa
- Create new metadata struct and type for python requirements. - Update parsing of python requirements to use python requirements metadata. - Remove extras and url from line. Add them to metadata instead. - Add unit test to test that extras are removed from package name. - Update test to look at requirements metadata. - Will need updated in future to support more than just == for the version constraint. - Update JSON schema data Closes anchore/grype#1246 Closes anchore/grype#1251 Signed-off-by: Shane Dell <shanedell100@gmail.com> |
||
|---|---|---|
| .. | ||
| generate.go | ||
| README.md | ||
| schema-1.0.0.json | ||
| schema-1.0.1.json | ||
| schema-1.0.2.json | ||
| schema-1.0.3.json | ||
| schema-1.0.4.json | ||
| schema-1.0.5.json | ||
| schema-1.1.0.json | ||
| schema-2.0.0.json | ||
| schema-2.0.1.json | ||
| schema-2.0.2.json | ||
| schema-3.0.0.json | ||
| schema-3.0.1.json | ||
| schema-3.1.0.json | ||
| schema-3.1.1.json | ||
| schema-3.2.1.json | ||
| schema-3.2.2.json | ||
| schema-3.2.3.json | ||
| schema-3.2.4.json | ||
| schema-3.3.0.json | ||
| schema-3.3.1.json | ||
| schema-3.3.2.json | ||
| schema-4.0.0.json | ||
| schema-4.1.0.json | ||
| schema-5.0.0.json | ||
| schema-5.0.1.json | ||
| schema-5.1.0.json | ||
| schema-6.0.0.json | ||
| schema-6.1.0.json | ||
| schema-6.2.0.json | ||
| schema-7.0.0.json | ||
| schema-7.0.1.json | ||
| schema-7.1.0.json | ||
| schema-7.1.1.json | ||
| schema-7.1.2.json | ||
| schema-7.1.3.json | ||
| schema-7.1.4.json | ||
| schema-7.1.5.json | ||
| vnd.syft+json | ||
JSON Schema
This is the JSON schema for output from the JSON presenters (syft packages <img> -o json and syft power-user <img>). The required inputs for defining the JSON schema are as follows:
- the value of
internal.JSONSchemaVersionthat governs the schema filename - the
Documentstruct definition withininternal/presenters/poweruser/json_document.gothat governs the overall document shape - the
artifactMetadataContainerstruct definition withinschema/json/generate.gothat governs the allowable shapes ofpkg.Package.Metadata
With regard to testing the JSON schema, integration test cases provided by the developer are used as examples to validate that JSON output from Syft is always valid relative to the schema/json/schema-$VERSION.json file.
Versioning
Versioning the JSON schema must be done manually by changing the JSONSchemaVersion constant within internal/constants.go.
This schema is being versioned based off of the "SchemaVer" guidelines, which slightly diverges from Semantic Versioning to tailor for the purposes of data models.
Given a version number format MODEL.REVISION.ADDITION:
MODEL: increment when you make a breaking schema change which will prevent interaction with any historical dataREVISION: increment when you make a schema change which may prevent interaction with some historical dataADDITION: increment when you make a schema change that is compatible with all historical data
Adding a New pkg.*Metadata Type
When adding a new pkg.*Metadata that is assigned to the pkg.Package.Metadata struct field it is important that a few things
are done:
- a new integration test case is added to
test/integration/catalog_packages_cases_test.gothat exercises the new package type with the new metadata - the new metadata struct is added to the
artifactMetadataContainerstruct withinschema/json/generate.go
Generating a New Schema
Create the new schema by running cd schema/json && go run generate.go (note you must be in the schema/json dir while running this):
- If there is not an existing schema for the given version, then the new schema file will be written to
schema/json/schema-$VERSION.json - If there is an existing schema for the given version and the new schema matches the existing schema, no action is taken
- If there is an existing schema for the given version and the new schema does not match the existing schema, an error is shown indicating to increment the version appropriately (see the "Versioning" section)
Note: never delete a JSON schema and never change an existing JSON schema once it has been published in a release! Only add new schemas with a newly incremented version. All previous schema files must be stored in the schema/json/ directory.