[FEATURE REQ] Automatically creating Version Set by Publisher based on API Version in OpenAPI specs

[ahmedbham]

Please describe the feature.

API Version can be specified in "version" field of Info Object in OpenAPI specification document. When creating an API using publisher by importing OpenAPI specification document, it would be very useful to automatically create Version Set based on version field value.

[github-actions]

  Thank you for opening this issue! Please be patient while we will look into it and get back to you as this is an open source project. In the meantime make sure you take a look at the [closed issues](https://github.com/Azure/apiops/issues?q=is%3Aissue+is%3Aclosed) in case your question has already been answered. Don't forget to provide any additional information if needed (e.g. scrubbed logs, detailed feature requests,etc.).
  Whenever it's feasible, please don't hesitate to send a Pull Request (PR) our way. We'd greatly appreciate it, and we'll gladly assess and incorporate your changes.

[guythetechie]

Sorry, this is out of scope for us. APIM doesn't use the version field in the OpenAPI specification that way. We'd run into conflicts between APIM's definition of a version set and what's defined in the OpenAPI spec.

[guythetechie]

If you can convince the APIM team to do this (automatically create a version set when importing a spec from the portal), then we'd be happy to add their implementation to ApiOps.