Create a new end-point to authenticate with Google Drive using OAuth
- Dominant language
- Python
- Stars
- 29
- Forks
- 13
- PR merge metrics
- No merged PRs in 30d
Description
The conclusions of [this spike](https://github.com/hypothesis/via3/issues/405):
* Nothing is certain with Google, it's all guesswork
* We can do two legged OAuth 2 quite easily with the Google libraries
* We seem to hit limits well below the stated quota with service accounts
* Round robining service accounts appears to get a higher total quota
* After enabling billing we appear to have got a much higher single account quota (no idea if this is the cause)
* Our caching is not effective with Google Drive due to `Vary: Origin`, `Vary: X-Origin` headers
Recommendations:
* Add a new Python end-point to Via 3 which will use the libraries to download Google Drive files
* Use a single account
* Emit headers to ensure the results can be cached
* Keep the old method behind a feature flag or other easily toggled change, so we can roll back if we hit issues
Notes
* Spike code here: https://github.com/hypothesis/via3/pull/410
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.