perses-cue-schema

Author Perses CUE schemas by defining panel, variable, or datasource types with package model and close({...}) constraints, then validate incrementally using percli plugin test-schemas. Import common types from github.com/perses/shared/cue/common.

Perses plugin schema validation requires CUE v0.12.0 or higher. You need this version to use the package model, close({...}) constraint patterns, and run percli plugin test-schemas successfully.

Yes, you can optionally generate Grafana migration files when providing JSON examples that validate against your Perses CUE schemas. The workflow supports creating panel, variable, or datasource schemas with migration compatibility.

Perses schema validation fails when you omit the package model declaration, skip close({...}) strict blocks, or miss required common type imports from github.com/perses/shared/cue/common. Follow the Phase 1-4 workflow and validate incrementally.

Structure Perses datasource CUE schemas by enforcing package model, importing shared common types, wrapping fields in close({...}) constraints, and providing validating JSON examples. Use percli plugin test-schemas for incremental validation checks.

Debug Perses CUE schema syntax by following the incremental validation workflow with percli plugin test-schemas, reviewing educational explanations for close({...}) patterns, and checking common type imports from the perses shared cue repository.