Skip to content
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

Closed
KotlinFactory opened this issue Aug 21, 2024 · 3 comments
Closed

Missing OpenAPI spec #261

KotlinFactory opened this issue Aug 21, 2024 · 3 comments
Labels
status:awaiting response Awaiting a response from the author status:stale Issue/PR is marked for closure due to inactivity

Comments

@KotlinFactory
Copy link

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

@KotlinFactory KotlinFactory changed the title Missing openai docs Missing openai spec Aug 21, 2024
@markmcd markmcd changed the title Missing openai spec Missing OpenAPI spec Aug 22, 2024
@markmcd
Copy link
Member

markmcd commented Aug 22, 2024

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.

Copy link

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.

@github-actions github-actions bot added the status:stale Issue/PR is marked for closure due to inactivity label Sep 10, 2024
Copy link

This issue was closed because it has been inactive for 27 days. Please post a new issue if you need further assistance. Thanks!

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Sep 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status:awaiting response Awaiting a response from the author status:stale Issue/PR is marked for closure due to inactivity
Projects
None yet
Development

No branches or pull requests

2 participants