OpenAPI 3.0 support

[kibertoad]

It seems that currently only OpenAPI 2.0 (Swagger) is supported. Considering how significant of an improvement 3.0 was, it would be great to have support for it as well.

[insafinou]

Hello,

do you have any news about it?

[qiwzhang]

Sorry, no update on this feature.

[qiwzhang]

@wyrickre may have update on this. But this is not in the ESP project scope.

[wyrickre]

We are evaluating this. Nothing to announce at this time, but keep checking back!

[baens]

This would be super awesome, because right now. v2 of the spec can't really handle multiple output versions. I.e. if I had 2 outputs (xml vs json) but wanted slightly different fields per object. In v2, this really can't be handled, in v3, the contents portion of the response can handle that.

[wyrickre]

We are evaluating OAS 3.0 support.

…

On Tue, Jul 16, 2019 at 8:31 AM Erik Lindblom ***@***.***> wrote: This would be super awesome, because right now. v2 of the spec can't really handle multiple output versions. I.e. if I had 2 outputs (xml vs json) but wanted slightly different fields per object. In v2, this really can't be handled, in v3, the contents portion of the response can handle that. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#446?email_source=notifications&email_token=AAPRNBBDES5Q2IJM6NXURJDP7XSU5A5CNFSM4FYZAGF2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD2BHUIQ#issuecomment-511867426>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAPRNBB734J2D22ZJLORZNLP7XSU5ANCNFSM4FYZAGFQ> .

[thees]

Any news?
Polymorphism with discriminators became much more useable in v3. We would appreciate that support alot!

[qiwzhang]

The current plan is to support it in the end of 2020.

[colesimmons]

Any updates?

[qiwzhang]

Sorry, not much progress for Cloud Endpoint. You may want to check out api-gateway. They may have plan to support it

[kostacasa]

Can confirm API gateway does not support OpenAPI Spec 3 either. But they both use Envoy Proxy under the hood, I wonder if there's a limitation there?

[qiwzhang]

It has nothing to do with Envoy. It is the Google endpoint service config compiler doesn't support OpenAPI spec. 3.0 yet.

[kostacasa]

Gotcha... looks like API gateway mostly wraps what cloud endpoints supports today so not sure if they are planning to take a path of their own in that regard

[davinchia]

@qiwzhang @wyrickre looks like plenty of users are asking for this. I understand this is the reason Google API Gateway doesn't support OAS 3.0 - we really want to use GCP, specifically API Gateway, but this is making us jump through lots of hoops that on fire while over lava in order to do so. Totally respect you have your own prioritisation process, but is there a way we can influence your backlog? As a member of the community, I would love to help everyone make a case for this.

[nika-pr]

Has anyone found an elegant solution yet as to how to use OepnAPI documents based on the OpenAPI 3.0 specification on Google Cloud, ideally managed/serverless?