This website requires JavaScript.
Explore
Help
Sign In
sartography
/
cr-connect-workflow
mirror of
https://github.com/sartography/cr-connect-workflow.git
Watch
1
Star
0
Fork
You've already forked cr-connect-workflow
0
Code
Issues
Packages
Projects
Releases
Wiki
Activity
907e1cbbb3
cr-connect-workflow
/
crc
History
Dan Funk
907e1cbbb3
minor fixes that were breaking when connecting to the front end.
2020-03-27 14:27:50 -04:00
..
api
minor fixes that were breaking when connecting to the front end.
2020-03-27 14:27:50 -04:00
models
minor fixes that were breaking when connecting to the front end.
2020-03-27 14:27:50 -04:00
scripts
Vastly more informative ApiError model that provides details on the underlying task where the error occured.
2020-03-27 08:29:31 -04:00
services
Vastly more informative ApiError model that provides details on the underlying task where the error occured.
2020-03-27 08:29:31 -04:00
static
Vastly more informative ApiError model that provides details on the underlying task where the error occured.
2020-03-27 08:29:31 -04:00
__init__.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
api.yml
Merge remote-tracking branch 'origin/master' into feature/status_refactor
2020-03-27 11:55:36 -04:00