SPIRE · API Governance Rules
SPIRE API Rules
Spectral linting rules defining API design standards and conventions for SPIRE.
9 Rules
error 3
warn 5
info 1
Rule Categories
spire
Rules
error
spire-operation-id-required
All operations must have an operationId.
$.paths[*][get,post,put,patch,delete,head,options]
warn
spire-operation-id-kebab-case
operationId must use camelCase starting with a verb (get, list, create, update, delete, enable, restore, kill).
$.paths[*][get,post,put,patch,delete].operationId
warn
spire-summary-title-case
Operation summaries must use Title Case.
$.paths[*][get,post,put,patch,delete].summary
warn
spire-tags-required
Every operation must have at least one tag.
$.paths[*][get,post,put,patch,delete]
error
spire-response-200-required
Every operation must define a 200 or 201 success response.
$.paths[*][get,post,put,patch,delete].responses
error
spire-servers-required
The API must define at least one server.
$
warn
spire-info-contact-required
The info object must include a contact entry.
$.info
warn
spire-no-trailing-slash
Paths must not have a trailing slash.
$.paths
info
spire-health-path-naming
Health check paths should follow the /live or /ready convention.
$.paths