Basic questions on the swagger promote script about apimanager-swagger-promote

[cwiechmann]

Hi @hakila, let me quickly answer your questions:

1. The only information used to identify an existing API is based on the exposure path. If you have two APIs exposed at the same time with the same path, I'm not sure what happens right now, but I guess it's the first returned by the REST-API. Swagger-Promote will always clean up existing APIs, as you basically have 1 API declared as desired and this should be reflected as this ONE and ONLY API in API-Manager.
2. The version number in API-Manager is just a meta information and basically has no impact in terms of Lifecycle. If you don't provide the version number in the config file and you see version 1.0, I assume API-Manager fills in by default 1.0. Swagger-Promote has no default handling implemented for the version number.
3. That's a valid use-case and I'll create a dedicated issue for that enhancement request to keep track of it. I have to think about it how to export the generated API-ID. I think it must be flexible enough to also export other information of the actual API.

[cwiechmann]

@hakila, I have created the issue #60 to support export of API-Details