-
Notifications
You must be signed in to change notification settings - Fork 20
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
Update OpenAPI schema to implement new operations #1564
Comments
Yes, this is basically the correct file, although it is a template for code generation is not the actual live file. The live file lives a bit deeper down. Do we have the schema definitions for each of these workflows? I am on vacation and am trying to keep up but not managing very well. |
@edeutsch Just following up on this now that you are back from vacation. Was the OW repo definitions what you meant by the schema definitions? |
Thanks for the reminder, Finn, the answer is yes. I started the update, but I think I am now blocked by this: I might be able to press ahead, but I'm fearing an explosion from the OpenAPI framework if I try to deploy it as is. |
Removing Finn, but this issue is still relevant, since we implement some additional operations but don't advertise it. See here for the ones we implement |
So assigning @edeutsch to updated the OpenAPI schema |
It looks to me like we are advertising exactly this list here: RTX/code/UI/OpenAPI/python-flask-server/openapi_server/openapi/openapi.yaml Lines 26 to 47 in 9cf40f7
So I am thinking this is done? Agree and close? Or let me know what is missing? |
This is already fixed, closing. |
@finnagin work with @edeutsch to figure out how to change this file (if that's even the right one) to properly advertise which operations we have implemented.
Bonus points if this can be done automatically any time operation_to_ARAXi.py is updated.
The text was updated successfully, but these errors were encountered: