Skip to content

recipe: validate constraint measurement paths at load time #1783

Description

@mchmarny

Follow-up to #1542 (design section 10). pkg/constraints.Evaluate distinguishes malformed constraint paths (ErrCodeInvalidRequest, now fails resolution closed) from values absent in the snapshot (ErrCodeNotFound, graceful exclusion by design). A grammatically valid but typo'd constraint path evaluates as NotFound and still degrades silently for unstated dimensions. Validate constraint paths against the measurement catalog when loading recipe data so typos fail at load time instead of masquerading as missing measurements.

Metadata

Metadata

Assignees

No one assigned

    Fields

    No fields configured for Enhancement.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions