-
Notifications
You must be signed in to change notification settings - Fork 739
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Missing OpenAPI spec #261
Comments
We don't use OpenAPI specs for our APIs, we use protocol buffer specs that are converted to discovery documents for, e.g. auto-generated client libraries. Here's the service definition in proto format, and here's the discovery URL (make sure you substitute your API key) I believe we can turn OpenAPI output on but I'd need to look into what trade-offs/compatibility issues there are, if any. Have you tried using a converter? e.g. gnostic will generate openapi from the proto def, and there are other tools that do discovery -> openapi, as well as catalogues of converted API specs. |
Marking this issue as stale since it has been open for 14 days with no activity. This issue will be closed if no further activity occurs. |
This issue was closed because it has been inactive for 27 days. Please post a new issue if you need further assistance. Thanks! |
Description of the feature request:
We need an OpenAPI spec for the gemini API.
The SpringAI team or some contributors would use this to implement Google Gemini directly into SpringAI. However this is not possible without reverse engineering code of existing clients like the python clients. (Which I would love not having to do)
See: spring-projects/spring-ai#1252
What problem are you trying to solve with this feature?
Google Gemini should be available for the server side Java/JVM world.
Any other information you'd like to share?
No response
The text was updated successfully, but these errors were encountered: