I'd like to see support for OAS 3.0 within the Dev Portal 4.X. Please see https://swagger.io/blog/announcing-openapi-3-0/ for reference. The simple reason ist that, Swagger 2.0 is cumbersome and inflexible in some areas.
this feature was planned for 4.3, which is 1 month late.
Thanks schje40, this is very helpful information. Please give this a high priority, since customers are already rejecting the API Management software due to the lack of support for OpenAPI 3.0.
This feature is on the product roadmap. Timing will be provided when the feature is assigned to a release.
Please, can we get feedback on this? There are many demands to this feature but no offical statement??
OpenAPI Specification 3.0.0 landed in July 2017. Can we have feedback on why it is not ready yet?
All our developer are pushing me to use the 3.0.x specification now and I'm the one who have to tell them to wait. I would really appreciate any feedback on wheter or not it is on the roadmap or even better, an ETA.
CA, can you let us know whether this is on the roadmap or not, and if so, for when?
One good reason for supporting OpenAPI 3.0 is this will support multiple host definitions, eg. for describing Dev, Test, Prod. Swagger 2.0 does not support this (API Host and Base Path | Swagger ).
This will help assisting in a setup with deployement to the Dev and UAT proxies, like described Manage API Deployments - CA API Developer Portal - 4.2 - CA Technologies Documentation . There is only 1 API definition in this setup and Swagger 2.0 can only describe for 1 host.
We would be very happy to see the OpenAPI 3.0 spec supported in the whole API management stack. Not only the API Portal, but also the API Gateway should be able to handle this. We have lots of customers building API's based on the OAS 3.0 and architectural regulations for governmental organisations even demand this.
CA API Management Community
Is there already any indication when support for OAS 3.0 will be implemented?