Ansible Automation Platform · API Governance Rules
Ansible Automation Platform API Rules
Spectral linting rules defining API design standards and conventions for Ansible Automation Platform.
12 Rules
error 5
warn 7
Rule Categories
info
no
operation
operationid
response
schema
security
servers
Rules
warn
info-title-prefix
Info title should start with "Ansible"
$.info
error
operation-operationId-required
Every operation must have an operationId
$.paths[*][get,post,put,patch,delete]
error
operation-summary-required
Every operation must have a summary
$.paths[*][get,post,put,patch,delete]
warn
operation-tags-required
Every operation must have tags
$.paths[*][get,post,put,patch,delete]
error
response-success-required
Operations must have success responses
$.paths[*][get,post,put,patch,delete].responses
error
security-global-defined
Global security must be defined
$
error
servers-https-only
Server URLs must use HTTPS.
$.servers[*].url
warn
operationid-casing
Operation IDs should be camelCase (the dominant convention in this API).
$.paths[*][get,post,put,patch,delete].operationId
warn
schema-names-casing
Component schema names should be PascalCase (the dominant convention in this API).
$.components.schemas
warn
schema-properties-casing
Schema properties should be snake_case (the dominant convention in this API).
$.components.schemas[*].properties
warn
security-schemes-defined
Security schemes should be defined in components.
$.components
warn
no-empty-descriptions
Descriptions must not be empty strings.
$..description