-
Notifications
You must be signed in to change notification settings - Fork 190
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
Support OpenAPI spec generation [ENHANCEMENT] #778
Comments
Hi @pandu-k, What's the current status of this issue? It seems like the OpenAPI spec generation is still not functional, as I'm unable to retrieve it from the expected /openapi.json endpoint. Additionally, the documentation in the README might need an update, as it implies that generating the OpenAPI spec is still supported, which doesn't seem to be the case. Could you provide any updates or guidance on how to proceed? Thanks! |
I’ve found a solution that restores OpenAPI spec generation and resolves the issue with the From my perspective, there are a few potential ways to address this:
I opted for the third approach since it was the simplest and most straightforward solution. Here are the specific changes I made:
After applying these modifications, the OpenAPI spec at I'm not entirely sure if this is the ideal long-term solution, but if it seems like a good fit, I’d be happy to submit a PR for it. |
Thanks @gabauer - we'll look into this |
Hello @gabauer , thanks for looking into this and raising a PR. I checked the source code and noticed that the ndarray type here is not used in any code or tests. I think it would be safe to remove it. Actually, the only type accepted for docs is |
Hi @papa99do, thanks for looking into it, I will check this out, try to let the tests run and add a test with a simple "is there" check on the openapi URIs to prevent breaking this stuff in the future. |
Hello @gabauer , sorry for the long wait. I've merged in your change after addressing the build permission issue. I've tested that the openAPI endpoints can be accessed again. I'll follow up to add more documentation and examples in following PRs. Thanks again for your contribution! |
Is your feature request related to a problem? Please describe.
In Marqo 2.x there isn't a way to generate OpenAPI spec. This was possible from the
/openapi.json
path.Describe the solution you'd like
An endpoint, usable from a running Marqo container, from which to retrieve the openapi specs.
Additional context
Relevant docs: https://fastapi.tiangolo.com/reference/openapi/docs/
The text was updated successfully, but these errors were encountered: