-
Notifications
You must be signed in to change notification settings - Fork 0
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
Create HTTP Client and Related Resolver for Program Service Endpoints in Gateway - Part 2 #703
Comments
Clients with the the four unchecked boxes are using program service endpoint with bugs. Once those bugs are cleared, I can do some testing. |
down to one last updateProgram endpoint which needs testing |
For one endpoint, https://program-service.dev.argo.cancercollaboratory.org/swagger-ui/index.html#/program-controller/updateProgram (updateProgram), we couldn't get the testing done before the end of the year. There is some update needed in ProgramService and Azher has been working on it before he needs to leave for wisdom tooth extraction. So I am leaving my code in Plateform-API to accept the payload that is required for this endpoint, and once ProgramService is updated, the updateProgram http client should work.
|
Discover a bug in ProgramService endpoint, createProgram, https://program-service.dev.argo.cancercollaboratory.org/swagger-ui/index.html#/program-controller/createProgram. I believe it's caused by the addition of DataCenterId property to the payload of this endpoint. |
Due to known issues w/ Program Service Create Program / Update Program, these resolvers will have to be tested once Program Service is updated |
PR: #694 |
program service clients:
This ticket has part 1 and part 2
The text was updated successfully, but these errors were encountered: