search

stephaneey / azure-apim-extension

Full Azure API Management suite and more VSTS extension
MIT License
66 stars 48 forks source link

Validation Error #40

Closed vaseems closed 5 years ago

vaseems commented 5 years ago

2019-03-06T10:21:38.1870541Z @{code=ValidationError; target=representation; message=Parsing error(s): JSON is valid against more than one schema from 'oneOf'. No valid schemas. Path 'paths./user.post.parameters[0]', line 1, position 879.} 2019-03-06T10:21:38.4594175Z ##[error]The remote server returned an error: (400) Bad Request.

Getting this error for the below swagger json

"/user": { "post": { "description": "description", "tags": [ "moveforward" ], "produces": [ "application/json" ], "parameters": [ { "in": "body", "schema": { "type": "array", "$ref": "#/definitions/Request" }, "description": "Process Description" } ], "responses": { "200": { "description": "users response", "schema": { "type": "object", "$ref": "#/definitions/Response" } } } } }

Definitions I have

"Request": { "type": "array", "items": { "type": "string" } }, "Response": { "type": "object" }

After repeated tries sometimes it works without any change.

Any help would be appreciated.

stephaneey commented 5 years ago

Hello,

The 400 error message is returned by the Azure Management API itself. The extension is not responsible for this. The extension simply forwards your JSON or YAML declaration to the Azure API, just make sure it is correct. Pay attention not to have weird chars in your document, certainly when working with the artifact and the code way of bringing your specs.