Assigned

Feature Request

Status Update

No update yet.

Description

mm...@google.com

created issue #1

Apr 19, 2018 02:05PM

Current status:
By the documentation [1] Google Cloud Endpoints accepts only version 2 of the OpenAPI Specification.

Desired feature:
Request for Google Cloud Endpoints to support OpenaAPI version 3.
_______
[1]:

https://cloud.google.com/endpoints/docs/openapi/openapi-limitations

Comments

jm...@google.com <jm...@google.com> #2Apr 19, 2018 06:44PM

Assigned to gc...@google.com.

I have forwarded this request to the engineering team. We will update this issue with any progress updates and a resolution.

Best Regards,
Josh Moyer
Google Cloud Platform Support

[Deleted User] <[Deleted User]> #3Jun 27, 2018 03:26AM

This is not only useful for IP addresses, but also for many other resources. I understand that names are currently used as identifiers, so this request is probably not trivial to implement. Maybe distinguishing between a (numeric, automatically generated) identifier and a (textual) label is the way to go?

ar...@gmail.com <ar...@gmail.com> #4Jul 11, 2018 09:45AM

Is it any hope? We have migrated our IP address to the server with different role, and now the name of this IP address resource doesn't match its role at all. It seems to be trivial enough to momentary reserve static IP address of the old named resource, drop resource, and immediately recreate it with the new name and the old IP address.

ja...@sherlock.co.nz <ja...@sherlock.co.nz> #5Aug 1, 2018 07:12AM

This would also improve life when using the Google Deployment Manager (since it otherwise error's out if you've changed a name of an IP)

ma...@gmail.com <ma...@gmail.com> #6Oct 24, 2018 01:30PM

Over 3 years to get something as basic as renaming a static IP address. Any progress here?

ap...@gmail.com <ap...@gmail.com> #7Nov 25, 2018 11:32PM

Yes, I have a customer who has this exact issue too! Any updates or workarounds would be very appreciated!

ma...@wisereducacao.com <ma...@wisereducacao.com> #8Nov 30, 2018 12:11PM

Any progress in here?

gr...@gmail.com <gr...@gmail.com> #9Dec 9, 2018 08:06AM

I would like this feature as well.

al...@cpu.host <al...@cpu.host> #10Jan 6, 2019 01:04PM

Hello, any progress in here? Please is very frustrating.

[Deleted User] <[Deleted User]> #11Feb 10, 2019 11:42PM

Hi, open request for more than 3 years for a simple change. Please proceed that.

[Deleted User] <[Deleted User]> #12Feb 14, 2019 02:30PM

+1. :(

hu...@gmail.com <hu...@gmail.com> #13Feb 22, 2019 11:34PM

We need this.

la...@idexx.com <la...@idexx.com> #14Mar 1, 2019 05:06PM

please add this!

du...@gmail.com <du...@gmail.com> #15Mar 10, 2019 03:53PM

+1 !

th...@carrefour.com <th...@carrefour.com> #16Mar 13, 2019 10:27AM

hb...@figarocms.fr <hb...@figarocms.fr> #17Mar 28, 2019 04:26PM

sp...@systemsbiology.org <sp...@systemsbiology.org> #18Apr 3, 2019 02:06AM

We need this please

[Deleted User] <[Deleted User]> #19Apr 10, 2019 05:32PM

mr...@gmail.com <mr...@gmail.com> #20Apr 23, 2019 10:43AM

+1

2018 =(

[Deleted User] <[Deleted User]> #21Apr 26, 2019 02:09PM

[Deleted User] <[Deleted User]> #22May 6, 2019 01:13PM

[Deleted User] <[Deleted User]> #23May 6, 2019 02:20PM

Message last modified on Sep 18, 2019 01:42PM

[Deleted User] <[Deleted User]> #24Jun 20, 2019 05:56PM

ta...@gmail.com <ta...@gmail.com> #25Jun 21, 2019 08:29AM

+1 (again) coming up to 5 years?

el...@replicant.ai <el...@replicant.ai> #26Jul 19, 2019 12:04AM

yo...@gmail.com <yo...@gmail.com> #27Jul 23, 2019 04:05AM

[Deleted User] <[Deleted User]> #28Jul 31, 2019 06:19AM

ma...@gmail.com <ma...@gmail.com> #29Aug 2, 2019 07:09AM

ga...@liveramp.com <ga...@liveramp.com> #30Aug 7, 2019 03:19AM

ni...@gmail.com <ni...@gmail.com> #31Aug 7, 2019 07:46PM

ro...@gmail.com <ro...@gmail.com> #32Aug 12, 2019 09:02PM

[Deleted User] <[Deleted User]> #33Aug 13, 2019 11:06PM

Please implement this

gr...@gmail.com <gr...@gmail.com> #34Sep 4, 2019 10:24AM

[Deleted User] <[Deleted User]> #35Sep 8, 2019 02:03AM

+1, don't see why this would be hard. If the underlying GCP infrastructure depends on the name remaining unchanged, then the frontend can simply provide a way to alias it such that the end-user doesn't have to see the "original" name anymore.

ro...@gmail.com <ro...@gmail.com> #36Sep 18, 2019 12:37PM

Bumping this.
Definitely useful feature at least provide a way to alias this.

+1

ci...@google.com <ci...@google.com> Sep 19, 2019 03:24PM

Reassigned to cl...@google.com.

co...@gmail.com <co...@gmail.com> #37Oct 5, 2019 01:37PM

[Deleted User] <[Deleted User]> #38Oct 9, 2019 07:56AM

ja...@dhimahi.com <ja...@dhimahi.com> #39Nov 7, 2019 10:59AM

ho...@gmail.com <ho...@gmail.com> #40Nov 16, 2019 06:20AM

+1 Please add this feature

shouldn't be a very difficult implementation but benefits lots of people

gr...@tonit.com <gr...@tonit.com> #41Nov 20, 2019 08:45PM

[Deleted User] <[Deleted User]> #42Jan 16, 2020 02:19PM

va...@gmail.com <va...@gmail.com> #43Jan 17, 2020 03:47AM

su...@wanderersbook.com <su...@wanderersbook.com> #44Jan 17, 2020 05:17PM

[Deleted User] <[Deleted User]> #45Jan 29, 2020 11:11AM

+1 (same goes for description). Should update in-place

x-...@qstream.com <x-...@qstream.com> #46Jan 29, 2020 11:14AM

+1 here too. But the problem is also with disks. We currently use part of hostname in the name. Sometimes a machine has to be renamed and it's not possible.

va...@extendaretail.com <va...@extendaretail.com> #47Jan 29, 2020 12:05PM

[Deleted User] <[Deleted User]> #48Jan 30, 2020 06:02PM

[Deleted User] <[Deleted User]> #49Feb 12, 2020 08:52AM

Guys, this feature was requested in 2014, what's the problem? Why hasn't this been implemented or at least an update been given??

kp...@gmail.com <kp...@gmail.com> #50Feb 12, 2020 05:40PM

+1
Whe the ETA for this simple important request?

[Deleted User] <[Deleted User]> #51Feb 12, 2020 05:49PM

At least say NO so we are not left hanging for years and years. If you are looking for a reason why Google you can't compete with Azure and AWS this thread would be a prime example. If Google can't respond to basic feature requests then it is easy to imagine they can't do other basic things. Did Elon Musk take over Google too? Are 1/2 of you Google employees fired or just too busy checking out Amazon prime deals working at home? WTF, crickets for 8+ years? Do Something!

ji...@groupecanam.com <ji...@groupecanam.com> #52Feb 12, 2020 08:49PM

kp...@gmail.com <kp...@gmail.com> #53Feb 13, 2020 01:07PM

tr...@directorschoice.com <tr...@directorschoice.com> #54Mar 3, 2020 05:58PM

Hello,

Thanks for reaching out to us!

The Feature Request has been created and the Product Engineering Team is working on this request. At this moment, there is no ETA to this request. Thank you for your trust and continued support to improve Google Cloud Platform products.

In case you want to report a new issue, please do not hesitate to create a new Issue Tracker thread describing your issue.

yj...@gmail.com <yj...@gmail.com> #55Mar 23, 2020 03:46PM

+1, this would be a very valuable feature.

hu...@gmail.com <hu...@gmail.com> #56Apr 10, 2020 02:19PM

mi...@devnull.org <mi...@devnull.org> #57Apr 15, 2020 01:40PM

fa...@rapidosoft.it <fa...@rapidosoft.it> #58Apr 15, 2020 02:07PM

I think it's better to move to other api gateway solutions.

cl...@google.com <cl...@google.com> Apr 15, 2020 11:32PM

Accepted by cl...@google.com.

[Deleted User] <[Deleted User]> #59Apr 23, 2020 09:10AM

gu...@gmail.com <gu...@gmail.com> #60Apr 24, 2020 07:35PM

as...@slb.com <as...@slb.com> #61May 6, 2020 03:07AM

ri...@gmail.com <ri...@gmail.com> #62May 12, 2020 10:35PM

am...@fairtility.com <am...@fairtility.com> #63May 18, 2020 06:53AM

ke...@tradecoverexchange.com <ke...@tradecoverexchange.com> #64May 19, 2020 09:27PM

What are other api gateway solutions? Seeing as this request is over two years old I don't see it getting there soon. Perhaps Google is not actually planning to make Endpoints OAS3 ready?

Any suggestions for alternatives?

ls...@hypertvx.com <ls...@hypertvx.com> #65May 22, 2020 09:16PM

j0...@gmail.com <j0...@gmail.com> #66Jun 26, 2020 11:42PM

he...@gmail.com <he...@gmail.com> #67Jun 29, 2020 01:44PM

sa...@ioannotator.com <sa...@ioannotator.com> #68Jun 29, 2020 01:44PM

[Deleted User] <[Deleted User]> #69Jun 29, 2020 01:45PM

[Deleted User] <[Deleted User]> #70Jul 1, 2020 08:22AM

gl...@gmail.com <gl...@gmail.com> #71Jul 4, 2020 12:50AM

cd...@urbn.com <cd...@urbn.com> #72Jul 20, 2020 05:47PM

[Deleted User] <[Deleted User]> #73Jul 21, 2020 10:48PM

We require this as well.

gk...@gmail.com <gk...@gmail.com> #74Jul 22, 2020 05:02PM

za...@codexhealth.com <za...@codexhealth.com> #75Jul 23, 2020 09:41PM

pa...@dlab.ie <pa...@dlab.ie> #76Jul 25, 2020 11:39AM

re...@gmail.com <re...@gmail.com> #77Jul 28, 2020 10:51PM

[Deleted User] <[Deleted User]> #78Jul 31, 2020 10:57AM

[Deleted User] <[Deleted User]> #79Aug 3, 2020 11:15AM

[Deleted User] <[Deleted User]> #80Aug 6, 2020 08:34AM

sh...@gmail.com <sh...@gmail.com> #81Aug 9, 2020 07:19AM

+1 :(

[Deleted User] <[Deleted User]> #82Aug 12, 2020 01:57PM

+1 AWS had this 2 ready years ago:

https://aws.amazon.com/about-aws/whats-new/2018/09/amazon-api-gateway-adds-support-for-openapi-3-api-specification/ please help

[Deleted User] <[Deleted User]> #83Aug 13, 2020 08:15AM

+1?

ex...@falabella.cl <ex...@falabella.cl> #84Aug 18, 2020 01:32AM

+1 :/

jj...@legacy.atrify.com <jj...@legacy.atrify.com> #85Aug 25, 2020 04:02PM

[Deleted User] <[Deleted User]> #86Sep 9, 2020 12:10PM

ar...@rm3l.org <ar...@rm3l.org> #87Sep 9, 2020 12:21PM

+1 This would be really great to have.
We currently make use of Quarkus with its implementation of Eclipse MicroProfile OpenAPI, which targets the OpenAPI v3 specification.
This issue prevents us from using Cloud Endpoints.

ju...@gmail.com <ju...@gmail.com> #88Sep 25, 2020 08:00PM

ka...@xsimple.org <ka...@xsimple.org> #89Sep 26, 2020 07:03PM

la...@gmail.com <la...@gmail.com> #90Sep 28, 2020 12:34PM

vo...@dhimahi.com <vo...@dhimahi.com> #91Sep 30, 2020 07:23PM

+10

na...@gmail.com <na...@gmail.com> #92Oct 15, 2020 12:03AM

any update??

cl...@google.com <cl...@google.com> #93Oct 15, 2020 12:21AM

We're targeting an alpha launch of OASv3 support for the new API Gateway product (nex gen Endpoints) in Q1 2021.

se...@gmail.com <se...@gmail.com> #94Oct 15, 2020 01:02AM

Looks like API Gateway only supports serverless backends (App Engine, Cloud Run & Cloud Functions) - is there a plan to add GKE support? Will API Gateway replace Endpoints eventually?

cl...@google.com <cl...@google.com> #95Oct 15, 2020 01:34AM

Would you mind posting that question to the API Gateway users Google group: https://groups.google.com/g/api-gateway-users

na...@gmail.com <na...@gmail.com> #96Oct 15, 2020 03:54AM

We also use Google Endpoints with gke services

ty...@medel.com <ty...@medel.com> #97Oct 16, 2020 11:38AM

jo...@totalenergies.com <jo...@totalenergies.com> #98Oct 23, 2020 12:33AM

+1, need GKE support

[Deleted User] <[Deleted User]> #99Nov 3, 2020 11:18PM

+1!

sh...@gmail.com <sh...@gmail.com> #100Nov 10, 2020 10:32AM

[Deleted User] <[Deleted User]> #101Nov 20, 2020 03:13PM

cl...@google.com <cl...@google.com> Nov 27, 2020 07:54PM

Assigned to sr...@google.com.

al...@pervasive-tech.com <al...@pervasive-tech.com> #102Jan 5, 2021 12:49PM

a....@katarinahealth.com <a....@katarinahealth.com> #103Feb 1, 2021 06:06PM

ry...@gmail.com <ry...@gmail.com> #104Feb 5, 2021 03:35PM

ja...@gmail.com <ja...@gmail.com> #105Feb 5, 2021 05:43PM

sa...@invintory.com <sa...@invintory.com> #106Feb 6, 2021 04:37PM

[Deleted User] <[Deleted User]> #107Feb 16, 2021 03:18AM

[Deleted User] <[Deleted User]> #108Feb 18, 2021 12:18AM

su...@overjet.ai <su...@overjet.ai> #109Feb 25, 2021 11:48AM

de...@boavistascpc.com.br <de...@boavistascpc.com.br> #110Mar 2, 2021 12:47PM

[Deleted User] <[Deleted User]> #111Mar 10, 2021 11:55AM

[Deleted User] <[Deleted User]> #112Mar 12, 2021 08:53AM

rb...@falabella.cl <rb...@falabella.cl> #113Mar 16, 2021 06:42PM

+ 1

al...@metrikus.io <al...@metrikus.io> #114Mar 17, 2021 05:04PM

ni...@propeldata.com <ni...@propeldata.com> #115Mar 19, 2021 05:02AM

ty...@propeldata.com <ty...@propeldata.com> #116Mar 24, 2021 10:10PM

ar...@gmail.com <ar...@gmail.com> #117Mar 25, 2021 08:21AM

[Deleted User] <[Deleted User]> #118Apr 19, 2021 05:09AM

[Deleted User] <[Deleted User]> #119Apr 19, 2021 01:26PM

ol...@gmail.com <ol...@gmail.com> #120Apr 26, 2021 06:47AM

jo...@gmail.com <jo...@gmail.com> #121Apr 26, 2021 11:54AM

bh...@gmail.com <bh...@gmail.com> #122May 5, 2021 02:09PM

> We're targeting an alpha launch of OASv3 support for the new API Gateway product (nex gen Endpoints) in Q1 2021.

As it is now Q2 2021, can we have any update of target date?

ad...@cross-entropy.com <ad...@cross-entropy.com> #123May 5, 2021 08:54PM

ro...@google.com <ro...@google.com> #124May 18, 2021 03:56PM

an...@sparc.agency <an...@sparc.agency> #125May 18, 2021 04:23PM

an...@sparc.agency <an...@sparc.agency> #126May 18, 2021 04:24PM

It's been 3 years since this was opened, when will we see OASv3?

ti...@fulfillmenttools.com <ti...@fulfillmenttools.com> #127May 21, 2021 03:02PM

Same here - we are waiting desperately for news on that topic! Is there any (yet another) timeline you can give us?

pa...@easy-ip.net <pa...@easy-ip.net> #128May 25, 2021 01:24PM

v....@gmail.com <v....@gmail.com> #129May 26, 2021 11:01AM

mi...@harbrdata.com <mi...@harbrdata.com> #130May 26, 2021 07:57PM

qi...@google.com <qi...@google.com> #131May 28, 2021 05:32PM

https://github.com/GoogleCloudPlatform/esp-v2/issues/500

[Deleted User] <[Deleted User]> #132Jun 11, 2021 05:40AM

jv...@harlemnext.com <jv...@harlemnext.com> #133Jun 15, 2021 12:15PM

cl...@gmail.com <cl...@gmail.com> #134Jun 17, 2021 08:20AM

ch...@imaware.com <ch...@imaware.com> #135Jun 21, 2021 02:13PM

This is really the only thing keeping us on AWS's API Gateway right now, would be nice to be able to switch over.

da...@gmail.com <da...@gmail.com> #136Jul 14, 2021 06:45AM

+1 this is making it really painful for us to choose to use API Gateway

Message last modified on Jul 14, 2021 07:29AM

[Deleted User] <[Deleted User]> #137Jul 19, 2021 02:50PM

de...@auspost.com.au <de...@auspost.com.au> #138Jul 21, 2021 11:29PM

+1 Require this for Endpoints - API Gateway does not suit our architecture (Not that it supports OAS 3.0 anyway by the sounds of it) and Apigee X is too heavy.

mi...@blerter.com <mi...@blerter.com> #139Jul 27, 2021 01:26AM

+1 Cloud Endpoints seem to be the only service out there that sticks to OAS 2.0, really hard to maintain two version of the same spec

Message last modified on Jul 27, 2021 01:27AM

it...@silohub.ag <it...@silohub.ag> #140Aug 20, 2021 02:02PM

sy...@brightedge.com <sy...@brightedge.com> #141Sep 1, 2021 11:10PM

+1 This would be great since we use FastAPI which only supports OAS 3.0 generation.

ma...@gmail.com <ma...@gmail.com> #142Sep 9, 2021 06:17AM

ma...@binx.io <ma...@binx.io> #143Sep 9, 2021 06:18AM

[Deleted User] <[Deleted User]> #144Sep 9, 2021 08:30AM

[Deleted User] <[Deleted User]> #145Sep 9, 2021 10:02AM

+1. I was just about to clean up our API by using the Cloud Endpoint. Swagger 2.0 _only_? You are kidding me.

[Deleted User] <[Deleted User]> #146Sep 9, 2021 11:15PM

+1

Any timeline projections here will really help. Until then, API gateway is going nowhere soon

Message last modified on Sep 9, 2021 11:16PM

[Deleted User] <[Deleted User]> #147Sep 10, 2021 10:22AM

I think my first bump on this thread was 2018 or 19. My son had graduated from college during the period and is now programming in Python.
Do you think he might see this?.

ra...@gmail.com <ra...@gmail.com> #148Sep 10, 2021 11:23AM

What is wrong here Google? It has been years since devs are asking for this. It is still not there!!!

m0...@gmail.com <m0...@gmail.com> #149Oct 2, 2021 05:29PM

My jaw dropped when I saw this in the docs - only swagger 2 - no OAS 3.0 (or better 3.1)? Then I saw this thread and I think my jaw fell of. How's this still not supported? I feel like getting pushed to use Apigee (which is way too expensive for our case) :/

mm...@type.hk <mm...@type.hk> #150Oct 14, 2021 01:06PM

st...@paperbox.ai <st...@paperbox.ai> #151Oct 26, 2021 11:22AM

bo...@gmail.com <bo...@gmail.com> #152Oct 26, 2021 09:31PM

dd...@google.com <dd...@google.com> #153Nov 17, 2021 05:01PM

ja...@gmail.com <ja...@gmail.com> #154Nov 19, 2021 07:28PM

Commenting +1 is futile. Instead use the STAR ⭐️ next to the issue ID.

fa...@rapidosoft.it <fa...@rapidosoft.it> #155Nov 21, 2021 07:34AM

I think the problem here is not the star :) Anyway, yes: almost 4 years of +1 proved their futility … and OpenAPI 3 is not yet available on gcloud :(

Message last modified on Nov 21, 2021 07:35AM

fu...@gmail.com <fu...@gmail.com> #156Dec 3, 2021 03:04PM

I'm lead developer in a fintech startup. We'd love to use Cloud Endpoints, but downgrading our tooling to v2 is not an option.

jj...@legacy.atrify.com <jj...@legacy.atrify.com> #157Jan 5, 2022 02:52PM

Same for us, downgrading to v2 is not an option.

kn...@gmail.com <kn...@gmail.com> #158Jan 12, 2022 09:40AM

ge...@gmail.com <ge...@gmail.com> #159Jan 19, 2022 10:59PM

Any updates????

st...@uman.ai <st...@uman.ai> #160Jan 24, 2022 03:53PM

Message last modified on Mar 31, 2022 01:01PM

[Deleted User] <[Deleted User]> #161Feb 22, 2022 04:54PM

al...@joinsherpa.com <al...@joinsherpa.com> #162Feb 22, 2022 08:50PM

AFAIK +1 comments are not as effective as setting the STAR ⭐️ next to the issue ID. I believe internally a count will assist with the priority whereas comments don't.

ni...@sportsdata.services <ni...@sportsdata.services> #163Mar 29, 2022 02:56PM

+1 and Starred.

e1...@gmail.com <e1...@gmail.com> #164Apr 20, 2022 03:07PM

ma...@gmail.com <ma...@gmail.com> #165Apr 21, 2022 08:33PM

wi...@gmail.com <wi...@gmail.com> #166Apr 28, 2022 10:07PM

gu...@gmail.com <gu...@gmail.com> #167May 12, 2022 08:41PM

sh...@gmail.com <sh...@gmail.com> #168May 14, 2022 08:24PM

al...@anecdotes.ai <al...@anecdotes.ai> #169May 15, 2022 07:21AM

+1 and starred

fr...@contibit.com <fr...@contibit.com> #170May 18, 2022 01:58PM

ol...@birdsview.no <ol...@birdsview.no> #171May 19, 2022 07:52AM

de...@atechcoins.com <de...@atechcoins.com> #172May 24, 2022 08:46AM

dn...@gmail.com <dn...@gmail.com> #173May 25, 2022 08:54AM

bc...@protonmail.com <bc...@protonmail.com> #174Jun 10, 2022 10:19PM

wi...@gmail.com <wi...@gmail.com> #175Jun 10, 2022 10:41PM

FWIW we gave up and decided to use krakend which does support openapi3.0 natively. and it runs in K8s no problemo.

sr...@google.com <sr...@google.com> Jun 20, 2022 05:18PM

Reassigned to fe...@google.com.

an...@fruver.com <an...@fruver.com> #176Jun 23, 2022 05:58AM

I want to know if this is going to be taken into account and added to endpoint and apigateway. I believe that they are giving more strength to GRPC.

an...@qyberion.com <an...@qyberion.com> #177Jul 16, 2022 02:52PM

As far as I understand, ESPv2 uses only a small subset of features of OpenAPI 2. This is also confirmed in this comment. All the schema definitions / messages are not part of it and I would argue that this part for improved schema design capability and request validations would be the main reason why we want to use OpenAPI 3. I guess it should be simple enough to define the API natively in OA3, then automatically remove all references to schema definitions and convert the remaining content into OA2. As far as I can tell, this part that is relevant for Cloud Endpoints / API Gateway is almost identical between OA2 and OA3. I guess the entire conversion workaround should not be too challenging once you exclude the messages.

However, I strongly believe this should be done automatically during the service deployment by Google. Why should every customer come up with their own conversion process and tooling? I'm certain this is better solved with a generic solution that is part of the service config deployment.

PS: Please, stop spamming everyone with meaningless "+1" comments, that's so 1990s Apache mailing list. There is a Vote button that has more effect and doesn't annoy other affected customers. Thank you!

m0...@gmail.com <m0...@gmail.com> #178Jul 16, 2022 05:47PM

Actually, I enjoy every +1 notification mail hitting my inbox because it tells me that other people do have the same issue as well. I don't get that for +1 votes ;)

br...@gmail.com <br...@gmail.com> #179Jul 16, 2022 09:21PM

More than 4 years for this (important) issue… +1 “tutta la vita”

de...@auspost.com.au <de...@auspost.com.au> #180Jul 17, 2022 10:44PM

Sorry #177 but... +1

iu...@heits.digital <iu...@heits.digital> #181Aug 6, 2022 05:54AM

+1 guys, I need to convert my 3.0 to 2.0 in order to make this work.

[Deleted User] <[Deleted User]> #182Sep 9, 2022 02:53PM

Any news about openAPI 3.0 support ???

is...@google.com <is...@google.com> Sep 20, 2022 07:46AM

Status: New

[Deleted User] <[Deleted User]> #183Sep 20, 2022 07:59AM

After all the feedback and votes it was finally ... unassigend xD

ys...@gmail.com <ys...@gmail.com> #184Sep 21, 2022 08:50AM

It's fine, we already change to aws, they support.

br...@gmail.com <br...@gmail.com> #185Sep 21, 2022 03:28PM

My open source project that no one cares about relies on Open API3. Please guys! Can we get this sorted?

le...@gmail.com <le...@gmail.com> #186Sep 23, 2022 01:37PM

ch...@ucsb.edu <ch...@ucsb.edu> #187Oct 31, 2022 06:26PM

+ 1

rm...@smartscm.com <rm...@smartscm.com> #188Nov 8, 2022 10:49AM

st...@gmail.com <st...@gmail.com> #189Nov 11, 2022 03:18PM

ma...@tryvital.io <ma...@tryvital.io> #190Nov 21, 2022 03:14PM

[Deleted User] <[Deleted User]> #191Nov 21, 2022 03:14PM

gu...@pagar.me <gu...@pagar.me> #192Nov 21, 2022 05:57PM

ke...@gmail.com <ke...@gmail.com> #193Dec 9, 2022 01:58PM

Soon it'll be old enough to go to elementary school.

Message last modified on Dec 11, 2022 01:39PM

bu...@haloanswer.com <bu...@haloanswer.com> #194Dec 19, 2022 11:33AM

This is goofy. :(

fa...@rapidosoft.it <fa...@rapidosoft.it> #195Dec 19, 2022 08:02PM

Google simply wants you to switch to Apigee 🤷‍♂️

be...@mail.schwarz <be...@mail.schwarz> #196Jan 3, 2023 12:20PM

[Deleted User] <[Deleted User]> #197Feb 14, 2023 02:58AM

+ 1

[Deleted User] <[Deleted User]> #198Mar 16, 2023 11:23PM

fa...@rapidosoft.it <fa...@rapidosoft.it> #199Mar 16, 2023 11:25PM

I love this issue… but really, it will never happens 🤷‍♂️

[Deleted User] <[Deleted User]> #200Mar 17, 2023 10:16AM

Hopefully just because 3.0 is outdated already and they'll go with 3.1 ...

c1...@heb.com <c1...@heb.com> #201Mar 30, 2023 06:13PM

Any plan to upgrade?

Message last modified on Mar 30, 2023 06:14PM

ke...@gmail.com <ke...@gmail.com> #202Mar 31, 2023 09:16AM

FYI, you can use OpenAPI3 today. You just need to use a library that converts OpenAPI3 to Swagger2 to satisfy google's needs (they use the swagger2 yaml file I believe to parse tokens before it arrives to your application). Note your application won't use the Swagger2 yaml file, that's only for google. Your app will run on OpenAPI3.

da...@cuyna.es <da...@cuyna.es> #203Apr 18, 2023 09:45AM

bo...@gmail.com <bo...@gmail.com> #204Apr 18, 2023 02:16PM

va...@google.com <va...@google.com> Apr 20, 2023 06:18AM

Assigned to ku...@google.com.

fa...@rapidosoft.it <fa...@rapidosoft.it> #205Apr 24, 2023 08:13AM

ku...@google.com may the force be with you

ku...@google.com <ku...@google.com> #206May 9, 2023 11:58PM

Reassigned to gc...@google.com.

Hello,

The Cloud Endpoints product engineering team has updated that OpenAPIv3 support will be limited to API Gateway and support for Endpoints will not be added. To expedite the process, I have reported the issue to the API Gateway product engineering team once again. However, please note that there is no ETA or implementation guarantee for this at this time. Rest assured, we’ll keep you updated on every update we receive from the team. Any further updates on this feature request will be communicated here.

ju...@gmail.com <ju...@gmail.com> #207Jul 4, 2023 08:47PM

Any news about openAPI 3.0 support ???

gi...@gmail.com <gi...@gmail.com> #208Jul 5, 2023 05:36PM

[Deleted User] <[Deleted User]> #209Jul 7, 2023 06:49AM

It's ridiculous that in order to deploy the YAML configuration file of my API I had to program an OpenApi 3 to Swagger 2 script because Google still can't support the industry standard. And libraries that implement Swagger 2 are starting to be deprecated with the newest versions of frameworks.

br...@gmail.com <br...@gmail.com> #210Jul 23, 2023 07:02AM

Still waiting for this :(

ma...@kallo.ai <ma...@kallo.ai> #211Aug 21, 2023 06:20PM

rn...@gmail.com <rn...@gmail.com> #212Aug 30, 2023 04:47AM

se...@deliveryhero.com <se...@deliveryhero.com> #213Aug 30, 2023 01:12PM

[Deleted User] <[Deleted User]> #214Aug 30, 2023 01:16PM

lu...@credix.finance <lu...@credix.finance> #215Sep 7, 2023 12:29PM

+1. It's been more than 3 years since this was open

fa...@rapidosoft.it <fa...@rapidosoft.it> #216Sep 7, 2023 12:32PM

It's already been more time than I wanted, so +1

ga...@latam.com <ga...@latam.com> #217Sep 26, 2023 01:24AM

li...@eqtventures.com <li...@eqtventures.com> #218Oct 3, 2023 06:47AM

+1 on this

[Deleted User] <[Deleted User]> #219Oct 3, 2023 08:20AM

What is the roadmap for Cloud Endpoints ? Should we consider Apigee X for all future API related questions from customer ?

au...@payclearly.com <au...@payclearly.com> #220Oct 13, 2023 04:31PM

Comment has been deleted.

Message last modified on Oct 13, 2023 04:32PM

e-...@gentera.com.mx <e-...@gentera.com.mx> #221Nov 14, 2023 12:14AM

Any update?

ja...@ubiquity.financial <ja...@ubiquity.financial> #222Dec 31, 2023 03:24AM

Im starting to regret using cloud endpoints for our project. Why is this so hard to get done, its been 5 years? Is Google deprecating Cloud Endpoints?

am...@yantrainc.com <am...@yantrainc.com> #223Feb 29, 2024 08:24AM

+1 Any update on this?

lu...@wonder-sys.com <lu...@wonder-sys.com> #224Apr 11, 2024 08:02AM

lu...@wonder-sys.com <lu...@wonder-sys.com> #225Apr 11, 2024 08:14AM

I used the npm cli app api-spec-converter to convert from openapi v3, hope this saves some time for anyone visiting here as google isn't really helping us on this issue

br...@clever.gy <br...@clever.gy> #226Apr 17, 2024 11:41AM

da...@gmail.com <da...@gmail.com> #227Jun 4, 2024 12:10AM

This one is funny.

+1

ju...@clever.gy <ju...@clever.gy> #228Jun 4, 2024 08:58AM

vn...@heb.com <vn...@heb.com> #229Jun 4, 2024 03:39PM

My team would also appreciate the addition of this feature. It would enable very useful automations for us.

va...@google.com <va...@google.com> Jun 10, 2024 09:58AM

Reassigned to va...@google.com.

va...@google.com <va...@google.com> #230Jun 20, 2024 12:56PM

Reassigned to gc...@google.com.

Hello,

Thank you for reaching out to us with your request.

We have duly noted your feedback and will thoroughly validate it. While we cannot provide an estimated time of implementation or guarantee the fulfillment of the issue, please be assured that your input is highly valued. Your feedback enables us to enhance our products and services.

We appreciate your continued trust and support in improving our Google Cloud Platform products. In case you want to report a new issue, Please do not hesitate to create a new issue on the Issue Tracker providing a detailed description of your issue.

Once again, we sincerely appreciate your valuable feedback; Thank you for your understanding and collaboration.

fa...@rapidosoft.it <fa...@rapidosoft.it> #231Jun 20, 2024 01:02PM

Don't worry, take all the time you need. It's not important to give us an idea of when or if OpenAPI 3.0 (3.1 at this point?) will be available. After all, this issue is only from 2018 and OpenAPI 3 from 2017.
I also ask you to forgive the out-of-place sarcasm... speaking of dates, it's probably because I'm a tired 1976

Message last modified on Jun 20, 2024 01:03PM

ve...@happtiq.com <ve...@happtiq.com> #232Jun 20, 2024 01:42PM

Personally, I would be okay with the announcement that this will never be supported by Cloud Endpoints under one condition:
Point us to a cost-sensitive (so not Apigee) solution of using OpenAPI version 3 on the Google Cloud.

ro...@gmail.com <ro...@gmail.com> #233Jul 23, 2024 02:32AM

co...@retailpath.xyz <co...@retailpath.xyz> #234Jul 23, 2024 03:12PM

a seemingly futile +1

pa...@unilever.com <pa...@unilever.com> #235Jul 26, 2024 11:53AM

I think they want to force us to use Apigee. There is no internal team working on this product. You can see release notes.

Message last modified on Jul 26, 2024 11:58AM

ve...@happtiq.com <ve...@happtiq.com> #236Jul 26, 2024 12:22PM

Then they would have to find an "Apigee Light" pricing for SMBs, the current options are not affordable if you only need a small subset of the Apigee features.

er...@gmail.com <er...@gmail.com> #237Aug 19, 2024 04:04AM

pa...@gmail.com <pa...@gmail.com> #238Aug 22, 2024 06:38AM

If you're not going to support this, make the base cost of Apigee's pay-as-you go model $0, so it's actually pay-as-you-go. Deploying some basic rate limiting with OpenAPI 3.0 support shouldn't cost $4,380/year.

jo...@gmail.com <jo...@gmail.com> #239Oct 25, 2024 04:46AM

It's disappointing that GCP API GAteway's OpenAPI 3 support is not going anywhere give how APIs is central to any app.

di...@gmail.com <di...@gmail.com> #240Dec 3, 2024 10:00PM

Its been almost 7years, what is the status of this?

ha...@cloudini.co <ha...@cloudini.co> #241Dec 4, 2024 10:22AM

I have a work around for this. Contact me via

cloudini.co

t....@gmail.com <t....@gmail.com> #242Dec 4, 2024 12:28PM

Yeah it's called AWS

to...@gmail.com <to...@gmail.com> #243Feb 20, 2025 05:41PM

7 years OMG could u please give an update about this?

Issue 78271318

Description

Issue summary

Comments

jm...@google.com <jm...@google.com> #2Apr 19, 2018 06:44PM

[Deleted User] <[Deleted User]> #3Jun 27, 2018 03:26AM

ar...@gmail.com <ar...@gmail.com> #4Jul 11, 2018 09:45AM

ja...@sherlock.co.nz <ja...@sherlock.co.nz> #5Aug 1, 2018 07:12AM

ma...@gmail.com <ma...@gmail.com> #6Oct 24, 2018 01:30PM

ap...@gmail.com <ap...@gmail.com> #7Nov 25, 2018 11:32PM

ma...@wisereducacao.com <ma...@wisereducacao.com> #8Nov 30, 2018 12:11PM

gr...@gmail.com <gr...@gmail.com> #9Dec 9, 2018 08:06AM

al...@cpu.host <al...@cpu.host> #10Jan 6, 2019 01:04PM

[Deleted User] <[Deleted User]> #11Feb 10, 2019 11:42PM

[Deleted User] <[Deleted User]> #12Feb 14, 2019 02:30PM

hu...@gmail.com <hu...@gmail.com> #13Feb 22, 2019 11:34PM

la...@idexx.com <la...@idexx.com> #14Mar 1, 2019 05:06PM

du...@gmail.com <du...@gmail.com> #15Mar 10, 2019 03:53PM

th...@carrefour.com <th...@carrefour.com> #16Mar 13, 2019 10:27AM

hb...@figarocms.fr <hb...@figarocms.fr> #17Mar 28, 2019 04:26PM

sp...@systemsbiology.org <sp...@systemsbiology.org> #18Apr 3, 2019 02:06AM

[Deleted User] <[Deleted User]> #19Apr 10, 2019 05:32PM

mr...@gmail.com <mr...@gmail.com> #20Apr 23, 2019 10:43AM

[Deleted User] <[Deleted User]> #21Apr 26, 2019 02:09PM

[Deleted User] <[Deleted User]> #22May 6, 2019 01:13PM

[Deleted User] <[Deleted User]> #23May 6, 2019 02:20PM

[Deleted User] <[Deleted User]> #24Jun 20, 2019 05:56PM

ta...@gmail.com <ta...@gmail.com> #25Jun 21, 2019 08:29AM

el...@replicant.ai <el...@replicant.ai> #26Jul 19, 2019 12:04AM

yo...@gmail.com <yo...@gmail.com> #27Jul 23, 2019 04:05AM

[Deleted User] <[Deleted User]> #28Jul 31, 2019 06:19AM

ma...@gmail.com <ma...@gmail.com> #29Aug 2, 2019 07:09AM

ga...@liveramp.com <ga...@liveramp.com> #30Aug 7, 2019 03:19AM

ni...@gmail.com <ni...@gmail.com> #31Aug 7, 2019 07:46PM

ro...@gmail.com <ro...@gmail.com> #32Aug 12, 2019 09:02PM

[Deleted User] <[Deleted User]> #33Aug 13, 2019 11:06PM

gr...@gmail.com <gr...@gmail.com> #34Sep 4, 2019 10:24AM

[Deleted User] <[Deleted User]> #35Sep 8, 2019 02:03AM

ro...@gmail.com <ro...@gmail.com> #36Sep 18, 2019 12:37PM

ci...@google.com <ci...@google.com> Sep 19, 2019 03:24PM

co...@gmail.com <co...@gmail.com> #37Oct 5, 2019 01:37PM

[Deleted User] <[Deleted User]> #38Oct 9, 2019 07:56AM

ja...@dhimahi.com <ja...@dhimahi.com> #39Nov 7, 2019 10:59AM

ho...@gmail.com <ho...@gmail.com> #40Nov 16, 2019 06:20AM

gr...@tonit.com <gr...@tonit.com> #41Nov 20, 2019 08:45PM

[Deleted User] <[Deleted User]> #42Jan 16, 2020 02:19PM

va...@gmail.com <va...@gmail.com> #43Jan 17, 2020 03:47AM

su...@wanderersbook.com <su...@wanderersbook.com> #44Jan 17, 2020 05:17PM

[Deleted User] <[Deleted User]> #45Jan 29, 2020 11:11AM

x-...@qstream.com <x-...@qstream.com> #46Jan 29, 2020 11:14AM

va...@extendaretail.com <va...@extendaretail.com> #47Jan 29, 2020 12:05PM

[Deleted User] <[Deleted User]> #48Jan 30, 2020 06:02PM

[Deleted User] <[Deleted User]> #49Feb 12, 2020 08:52AM

kp...@gmail.com <kp...@gmail.com> #50Feb 12, 2020 05:40PM

[Deleted User] <[Deleted User]> #51Feb 12, 2020 05:49PM

ji...@groupecanam.com <ji...@groupecanam.com> #52Feb 12, 2020 08:49PM

kp...@gmail.com <kp...@gmail.com> #53Feb 13, 2020 01:07PM

tr...@directorschoice.com <tr...@directorschoice.com> #54Mar 3, 2020 05:58PM

yj...@gmail.com <yj...@gmail.com> #55Mar 23, 2020 03:46PM

hu...@gmail.com <hu...@gmail.com> #56Apr 10, 2020 02:19PM

mi...@devnull.org <mi...@devnull.org> #57Apr 15, 2020 01:40PM

fa...@rapidosoft.it <fa...@rapidosoft.it> #58Apr 15, 2020 02:07PM

cl...@google.com <cl...@google.com> Apr 15, 2020 11:32PM

[Deleted User] <[Deleted User]> #59Apr 23, 2020 09:10AM

gu...@gmail.com <gu...@gmail.com> #60Apr 24, 2020 07:35PM

as...@slb.com <as...@slb.com> #61May 6, 2020 03:07AM

ri...@gmail.com <ri...@gmail.com> #62May 12, 2020 10:35PM

am...@fairtility.com <am...@fairtility.com> #63May 18, 2020 06:53AM

ke...@tradecoverexchange.com <ke...@tradecoverexchange.com> #64May 19, 2020 09:27PM

ls...@hypertvx.com <ls...@hypertvx.com> #65May 22, 2020 09:16PM

j0...@gmail.com <j0...@gmail.com> #66Jun 26, 2020 11:42PM

he...@gmail.com <he...@gmail.com> #67Jun 29, 2020 01:44PM

sa...@ioannotator.com <sa...@ioannotator.com> #68Jun 29, 2020 01:44PM

[Deleted User] <[Deleted User]> #69Jun 29, 2020 01:45PM

[Deleted User] <[Deleted User]> #70Jul 1, 2020 08:22AM

gl...@gmail.com <gl...@gmail.com> #71Jul 4, 2020 12:50AM

cd...@urbn.com <cd...@urbn.com> #72Jul 20, 2020 05:47PM

[Deleted User] <[Deleted User]> #73Jul 21, 2020 10:48PM

gk...@gmail.com <gk...@gmail.com> #74Jul 22, 2020 05:02PM

za...@codexhealth.com <za...@codexhealth.com> #75Jul 23, 2020 09:41PM