Move fetch api definition feature to Zally API

The web ui currently does the fetching of an api definition which is given via an url by the user. The web ui implements this on server side in Node.

Let’s discuss if we should change our Zally API to also accept links to api definition files. There are different ways of designing this:

• adding new endpoint only for urls
• adding new optional field in payload of current api-violations endpoint
• transparently accepting a link in current api_definitionfield

Looking for feedback from you, @netme @mkulak @rbarilani. Do you wanna have this in Zally API? And if yes, which design do you prefer?

[netme]

Btw, we should also move it out of cli component.

[fmueller]

Ok, then we’ll go with option 2:

• adding api_definition_url field
• making both fields, api_definition and api_definition_url, optional
• returning BAD_REQUEST if none of them is in the request or both (the API only accepts one field at once)