Argo Workflows · API Governance Rules
Argo Workflows API Rules
Spectral linting rules defining API design standards and conventions for Argo Workflows.
13 Rules
error 5
warn 6
info 2
Rule Categories
info
no
operation
parameter
paths
response
security
Rules
warn
info-title-prefix
API title must start with "Argo Workflows"
$.info.title
error
info-description-required
API must have a description
$.info
error
operation-summary-required
Every operation must have a summary
$.paths[*][get,post,put,delete,patch]
warn
operation-summary-prefix
Operation summaries must start with "Argo Workflows"
$.paths[*][get,post,put,delete,patch].summary
error
operation-operationid-required
Every operation must have an operationId
$.paths[*][get,post,put,delete,patch]
warn
operation-tags-required
Every operation must have at least one tag
$.paths[*][get,post,put,delete,patch]
info
paths-versioned
All paths should be versioned
$.paths[*]~
info
paths-kebab-case
Path segments should use kebab-case or camelCase
$.paths[*]~
error
response-success-required
Every operation must define at least one response
$.paths[*][get,post,put,delete,patch].responses
warn
response-description-required
All responses must have a description
$.paths[*][get,post,put,delete,patch].responses[*]
warn
security-definitions-required
API must define security schemes
$
error
no-empty-summaries
Summaries must not be empty
$.paths[*][get,post,put,delete,patch].summary
warn
parameter-description-required
Parameters should have descriptions
$.paths[*][get,post,put,delete,patch].parameters[*]