cops release policy validate checks the release gate configuration in cops.project.json for structural errors before you run cops release check. Use it after editing cops.project.json to catch issues like duplicate gate IDs, unsupported gate types, invalid parameters, and expired waivers.
Usage
Flags
Validate only the named project from the
projects map. When omitted, all projects in the config are validated.Output format:
table, json, or markdown.Output columns
project, check, status, details
| Check | Description |
|---|---|
gates_defined | pass when at least one gate is configured; warn when no gates are defined |
gate_id_unique | fail when a gate ID is duplicated within a project |
gate_type_supported | fail when a gate type is not in the supported list |
gate_schema | fail when a gate is missing required params for its type |
sla_hours_valid | fail when slaHours is set to a non-positive value |
owner_present_for_ticket | warn when ticket is set but owner is missing |
waiver_expiry_format | fail when waiverExpires is not a valid ISO datetime |
waiver_expiry_future | warn when waiverExpires is in the past |
waiver_expiry_present | warn when waiver is set but waiverExpires is missing (waiver never expires) |
Exit codes
| Code | Meaning |
|---|---|
0 | All checks passed |
10 | One or more warnings found (e.g. no gates configured, expired waiver) |
30 | One or more validation failures or cops.project.json not found |
Examples
Run
cops release policy validate after editing cops.project.json and before running cops release check to catch configuration errors early without making API calls.Related
cops release check
Run the validated gates against live product APIs.
Configuration guide
Full reference for cops.project.json structure and gate fields.