Sysdig · API Governance Rules
Sysdig API Rules
Spectral linting rules defining API design standards and conventions for Sysdig.
10 Rules
error 4
warn 5
info 1
Rule Categories
sysdig
Rules
error
sysdig-operation-ids-required
All operations must have an operationId defined.
$.paths[*][get,post,put,delete,patch]
error
sysdig-operation-summary-required
All operations must have a summary.
$.paths[*][get,post,put,delete,patch]
warn
sysdig-operation-summary-title-case
Operation summaries must use Title Case.
$.paths[*][get,post,put,delete,patch].summary
error
sysdig-bearer-auth-required
API must define Bearer token authentication.
$.components.securitySchemes
warn
sysdig-tags-defined
All operations must have at least one tag.
$.paths[*][get,post,put,delete,patch]
error
sysdig-responses-200-defined
GET operations must have a 200 response.
$.paths[*].get
warn
sysdig-error-responses-defined
Operations should define 401 or error responses.
$.paths[*][post,put,delete]
warn
sysdig-request-body-post
POST operations should have a request body.
$.paths[*].post
warn
sysdig-path-versioned
API paths should include a version prefix (/api/v1/, /api/v2/, /api/v3/).
$.paths[*]~
info
sysdig-schema-descriptions
Schema properties should have descriptions.
$.components.schemas[*].properties[*]