cr-connect-workflow/crc/api
Dan Funk 53255ef35e massive overhaul of the Workflow API endpoint.
No Previous Task, No Last Task, No Task List.  Just the current task, and the Navigation.
Use the token endpoint to set the current task, even if it is a "READY" task in the api.
Previous Task can be set by identifying the prior task in the Navigation (I'm hoping)
Prefering camel case to snake case on all new apis.  Maybe clean the rest up later.
2020-05-15 15:54:53 -04:00
..
__init__.py Adding file management. Files are stored in the database along with basic meta data. 2019-12-27 13:50:03 -05:00
common.py Vastly more informative ApiError model that provides details on the underlying task where the error occured. 2020-03-27 08:29:31 -04:00
file.py No longer requires task_id 2020-05-06 14:27:28 -04:00
study.py Refactor the stats models, and assure they are very correct across all tests with the workflow api. 2020-05-04 10:57:09 -04:00
tools.py Adding a simple endpoint that describes what scripts are currently available, along with a brief description. 2020-03-03 15:30:42 -05:00
user.py It became impossible to use the Swagger ui when we started adding authentication to all of the calls. I discovered Connexion and Swagger have a default way of handing JTW authentication and this cleans up our code quite a bit, moves the securing of endpoints into the API Definition, which is quite nice, and removes a whole library dependency (I never get to do that!) I added a SWAGGER_AUTH_KEY that can be used in non-production environments to allow users to quickly authenticate from the Swagger ui. I also removed all api calls to simple little happy api services, because that is just mean and pointless. 2020-03-24 14:15:21 -04:00
workflow.py massive overhaul of the Workflow API endpoint. 2020-05-15 15:54:53 -04:00