[META] Semantic validations

[ycombinator]

The package spec allows for syntactic validations of packages. These validate the structure of package contents. They have been implemented via #14, #41, and several minor follow up PRs.

There is also a need for semantic validations. These validate that values found in package contents conform to further rules that may not be expressible in the spec itself. For example:

• Validate that icon and screenshot sources exist: Validate the icon and screenshot sources exist #31
• Validate that dashboard IDs start with package names: Validate that Kibana asset IDs start with lowercase package names #65
• Ensure consistency between CHANGELOG and manifest: Semantic validation: ensure consistency between version and changelog #167

[ruflin]

• Validation for ingest pipelines: https://github.com/elastic/package-registry/blob/master/util/dataset.go#L168

[ycombinator]

Hey @ruflin, I'm starting to look into this issue now. Could you elaborate on your comment (#47 (comment)) please? The link in the comment is now dead so I can't figure out what you meant. Thanks!

[ruflin]

If I remember correctly this was about validating that a pipeline name that was used in the manifest actually exists. Basically any file that can be referenced from the manifest file like icons, readmes, pipelines, etc. should be validated that it exists.

[mtojek]

@ycombinator Would you mind updating the status of this issue? You have made a significant progress here recently.

[ycombinator]

There is no direct update to this issue because of the recent progress. However, I updated #65 which is linked from this issue.

Separately, I also added #167 to the checklist on this issue.

[jsoriano]

Checklist was completed, closing this. Please open new issues for additional validations.