4b7e7b789f## Small improvements for the autoinstallation schema - Added product name examples (so they are used in autocompletion) - Allow using "$schema" key for linking the schema definition, some editors like VSCode use that for validating the JSON file automatically when pointed to the schema location - Use "agama-project" in the GitHub URLs ## Testing Tested in local VSCode and the online [VSCode for web](https://vscode.dev/): <img width="1042" height="945" alt="vscode-agama-profile-products" src="https://github.com/user-attachments/assets/ebdf27c7-d99c-44cb-bb56-8fe5ccd97600" /> |
||
|---|---|---|
| .. | ||
| examples | ||
| .gitignore | ||
| examples space | ||
| examples%20percent | ||
| iscsi.schema.json | ||
| package-lock.json | ||
| package.json | ||
| profile.schema.json | ||
| README-weird-filenames.md | ||
| README.md | ||
| storage.model.schema.json | ||
| storage.schema.json | ||
JSON schema definition
See the JSON schema documentation for more details. The Agama schemas uses the Draft 2019-09 version.
Autoinstallation profile
The Agama autoinstallation profile JSON schema is defined in these files:
- profile.schema.json (the main definition)
- storage.schema.json (referenced from the main definition)
- iscsi.schema.json (referenced from the main definition)
Agama REST API
The storage.model.schema.json file describes the structure of the storage data passed via the internal REST API. This is important only for Agama developers, it is not intended to be used by end users.
Validation
To verify that the definitions are correct run these commands:
# install needed NPM packages
npm ci
# verify the schema
npm run validate
These commands are run in the CI automatically whenever a schema file is modified.