cr-connect-workflow/crc/api
Aaron Louie 9afcd753c4 No longer requires task_id 2020-05-06 14:27:28 -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 I had to give up and live with the idea that we can only render documentation on the current task, not on the previous or next tasks. I think this is ok. If you want to view a task, you need to make it the active task to assure all the parts and pieces are in place. 2020-05-06 13:01:38 -04:00