Validate Azure REST API Specifications
npm install oavbash
npm install -g oav@latest
`
#### Command usage:
`bash
$ oav -h Commands:
analyze-dependency analyze swagger resource type
dependency.
example-quality Performs example quality validation
of x-ms-examples and examples
present in the spec.
extract-xmsexamples Extracts the x-ms-examples for a
given swagger from the .NET session
recordings and saves them in a file.
generate-examples [spec-path] Generate swagger examples from real
payload records.
validate-example Performs validation of x-ms-examples
and examples present in the spec.
validate-spec Performs semantic validation of the
spec.
validate-traffic Validate traffic payload against the
spec.
traffic-convert Showcase what it would look like to
transform a directory full of
azure-sdk/test-proxy
recordings files into traffic payloads
consumable by traffic validation command in oav
Options:
--version Show version number [boolean]
-l, --logLevel Set the logging level for console.
[choices: "off", "json", "error", "warn", "info", "verbose", "debug", "silly"]
[default: "info"]
-f, --logFilepath Set the log file path. It must be an absolute filepath. By
default the logs will stored in a timestamp based log file
at "/home/ruowan/oav_output".
-p, --pretty Pretty print
-h, --help Show help [boolean]
`
$3
- Semantic validation
Semantic validation enforces correctness on the swagger specific elements. Such as paths and operations. Ensure the element definition meet the OpenApi 2.0 specification.
- Model validation
Model validation enforces correctness between example and swagger. It checks whether definitions for request parameters and responses, match an expected input/output payload of the service.
Examples of issues detected:
- Required properties not sent in requests or responses
- Defined types not matching the value provided in the payload
- Constraints on properties not met
- Enumeration values that don’t match the value used by the service.
Model validation _requires_ example payloads (request/response) of the service, so the data can be matched with the defined models. See x-ms-examples extension on how to specify the examples/payloads. Swagger “examples” is also supported and data included there is validated as well. To get the most benefit from this tool, make sure to have the simplest and most complex examples possible as part of x-ms-examples.
- Please take a look at the redis-cache swagger spec as an example for providing "x-ms-examples" over here.
- The examples need to be provided in a separate file in the examples directory under the api-version directory azure-rest-api-specs/arm-. You can take a look over here for the structure of examples.
- We require you to provide us a minimum (just required properties/parameters of the request/response) and a maximum (full blown) example. Feel free to provide more examples as deemed necessary.
- We have provided schemas for examples to be provided in the examples directory. It can be found over here. This will help you with intellisense and validation.
- If you are using vscode to edit your swaggers in the azure-rest-api-specs repo then everything should work out of the box as the schemas have been added in the .vscode/settings.json file over here.
- If you are using Visual Studio then you can use the urls provided in the settings.json file and put them in the drop down list at the top of a json file when the file is opened in VS.
$3
Swagger specs validation could be split in the following:
1. Schema validation
2. Semantic validation
3. Model definition validation
4. Swagger operations execution (against mocked data or live tests)
5. Human-eye review to complement the above
In the context of “azure-rest-api-specs” repo:
- #1 is being performed on every PR as part of CI.
- #2 and #3 are performed by the tool currently in openapi-validation-tools repo and by AutoRest linter. We’re working towards integrating them into CI for “azure-rest-api-specs” repo.
- #4 is not available yet, though we’re starting to work on it.
- #5 will be done by the approvers of PRs in “azure-rest-api-specs”, as this won’t be automated.
$3
OAV support run API test against Azure and validate request and response. You could define API scenario file which compose with several swagger example files and then use oav to execute it. For more details about API test, please refer to this API scenario documentation.
$3
- A Live Validation mode has been added to OAV with the purpose of enabling validation of live traffic.
- Usage (here is a sample of a request-response pair):
`javascript
const liveValidatorOptions = {
git: {
url: "https://github.com/Azure/azure-rest-api-specs.git",
shouldClone: true,
},
directory: path.resolve(os.homedir(), "cloneRepo"),
swaggerPathsPattern: "/specification//resource-manager//*.json",
isPathCaseSensitive: false,
shouldModelImplicitDefaultResponse: true,
};
const apiValidator = new oav.LiveValidator(liveValidatorOptions);
await apiValidator.initialize(); // Note that for a large number of specs this can take some time.
// After initialize() finishes we are ready to validate
const validationResult = apiValidator.validateLiveRequestResponse(requestResponsePair);
`
$3
Output of the OAV tool has been snapshotted and committed to the repo. The regression test may be run on a sample or all of https://github.com/azure/azure-rest-api-specs. If there are changes to the snapshots the build produces a git patch file as an artifact which may be used to update the snapshots.
Fast Regression (~10mins) is used for merge validation
Slow Regression (~1 hour) is run after merge and should be fixed if it fails
#### Fixing regression builds
1. Go to the failed build
2. Download the artifact patch file
3. In the OAV directory run git apply