A rules engine over infrastructure definitions, fetched at run time, with a version hash that blocks publication against a stale rule set.
Assess runs before anything is built. The service definition is checked against a rule set covering the deployment manifest, the API definition, and the security, distribution, identity and logging conventions every service is required to follow.
The rules are fetched at run time rather than vendored into each repository, so tightening a rule is one edit at the source and the next build everywhere picks it up.
How it works
One rule carries the most weight. Named EndpointDocumentationNotExists, it asserts that every endpoint declared in the deployment manifest also appears in the API definition — checked on every build, blocking the build where it did not hold.
No endpoint could be released undocumented, so the API definitions stayed at their canonical paths and each service's contract surface is readable off its repository.
Publication is gated on a version hash over the joined rule hashes. Three naming rules are excluded from the join, and their absence in any form makes every generated hash differ — the note on record says the hash is deliberately broken in that case, to stop a broken version publishing.
When a component linked to Assess publishes, the catalogue reads the bundle's hash, compares it against the last one recorded, and updates the hash required for publication when it differs. A build against a stale rule set therefore fails at publication rather than shipping quietly.
Operations
Assess
POST/assessments
Create Assessment
new-assessment
Assess validates a bundle of source code (Identified by a source_url) according to the rules configured for Assess.
Assess returns an assessment_id in the response body. To retrieve the results of the validation, call Retrieve Assessment Status with the assessment_id.
Path of the property or location issue in your file
file
string
Assessed file
message
string
Error message
rule_code
string
Rule code
source_url
string
Presigned URL with the assessed bundle and including metadata in the header for Assess and other products. This metadata is in use as a signature of successful assessment.
status
string
Status of assessmentFAILEDFAULTIN_PROGRESSNOT_FOUNDSTOPPEDSUCCEEDEDTIMED_OUT
metadata
object
Assessment metadata plus metadata included in the assessment presigned URL coming from other products
logs
string
Contains log on failed assessment
warnings
object
Contains warnings on assessment
errors
object[]
Errors array
message
string
Error message
path
string
Path of the property or location issue in your file
file
string
Assessed file
message
string
Error message
rule_code
string
Rule code
Other responses
400401403404
POST/assessments/overview
Create Overview Assessment
new-overview-assessment
Create Assessment Overview
Assess Overview validates an input of overview in String format according to the rules configured for Assess.
Assess returns an assessment_id in the response body. To retrieve the results of the validation, call Retrieve Assessment Status with the assessment_id.
Assess Swagger validates an input of swagger in JSON format according to the rules configured for Assess.
Assess returns an assessment_id in the response body. To retrieve the results of the validation, call Retrieve Assessment Status with the assessment_id.