oav
oav copied to clipboard
Azure
Tools for validating OpenAPI (Swagger) files.
Currently there is some access storage account via access key in different swagger tools which is not recommend by SDL. we should change them to access by manageIdentity
Hi, I've been trying everything I could to figure out why "instantiating" a new instance of the discriminating schema didn't work for me. The below is my schema and x-ms-examples:...
I’m looking at the [AutoRest authentication documentation on GitHub](https://github.com/Azure/autorest/blob/main/docs/generate/authentication.md), where it says that I can declare that my REST API uses AAD Token authentication in Swagger 2.0 like this: ```json...
In function validateRequest, model validate can only get parameters under request methods, public parameters will be missed For example: ``` json "paths": { "(path)": { "parameters": [A, B, C] "put":...
``` ➜ oav generate-examples openapi.json { message: `fatal error: ENOENT: no such file or directory, open 'https:/raw.githubusercontent.com/Azure/azure-rest-api-specs/main/specification/common-types/resource-management/v3/types.json', {"errno":-2,"code":"ENOENT","syscall":"open","path":"https:/raw.githubusercontent.com/Azure/azure-rest-api-specs/main/specification/common-types/resource-management/v3/types.json"}`, level: '\x1B[31merror\x1B[39m' } fatal error: ENOENT: no such file or directory, open...
when running `oav validate-spec (a github url for the spec path)`, it will report JSON_PARSING_ERROR for example: ``` oav validate-spec https://github.com/Azure/autorest.testserver/blob/main/swagger/azure-special-properties.json Semantically validating https://github.com/Azure/autorest.testserver/blob/main/swagger/azure-special-properties.json Errors reported: code: JSON_PARSING_ERROR message: 'Json...