Add json-schema for pod-specifications. #911
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Enables completion and validation in editors that support json-schema.
To test, download the schema and add the following property to a pod-specification file:
Once the schema is published, we should then require the
$schema
(instead of"version": 1
), thus identifying the document and its version.Basically, pod-specifications should then always have:
Also note: json-schemas work for yaml files too, as long as the yaml-extension (from Red Hat) is installed. However, they want the schema as comment:
We could make this a requirement for our pod specifications (if written in YAML).