URL for Swagger-Definitions about apimanager-swagger-promote

[rchinthakuntla]

+1

[cwiechmann]

Hi @rchinthakuntla, @rathnapandi, I'm planning to implement this feature now.

Even if the API-Manager supports the direct import of Swagger-Files from a URL, the tool must pull the Swagger-File locally, to be able to compare it with the actual API.

I plan the following:
Additionally to declare the Swagger-File by: -a <path_to_local_swagger_file>, users can reference a Swagger-File by:

• providing a file: -a my_swagger.url
  The key will be the file-extention ".url" and in that case the following content is expected:
  user/password@https://any.host.com/path/xyz/swagger.json
  With that an API-Service-Provider still has the option to programmatically reference a Remote-Swagger-File, still triggering a CI/CD-Flow. The triggered CI/CD-System, running Swagger-Promote, will have to pull down the Swagger-File and needs access to that endpoint.

• providing a URL directly: -a user/password@https://any.host.com/path/xyz/swagger.json
  This is useful when the tool is started interactively just by providing the right URL.

Both option will optionally support HTTP-Basic AuthN.

Any thoughts on this? Would that work?

[cwiechmann]

Added support for it with version 1.4.0.