-
Notifications
You must be signed in to change notification settings - Fork 67
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
How do I use it for backend that requires token? #12
Comments
did you find a solution? |
so the |
@Jancis No, it's mostly an access and renew token (within a jwt token). Without this, you can't use dropbox or similar services that use OAuth2 since the token changes from time to time (gets renewed by rclone) and needs to be persisted somewhere. |
Oh, sounds like chicken and egg problem where You need to mount a rwx storage on all rclone plugin pods and share the token, but You don't have any :) I had some success with nfs-subdir-external-provisioner and a custom nfs server. If You mount a storage with rclone in it, You might have more or less the same system (but the storage is mounted in a single pod then). If You customize the nfs server, You could store and persist the token. |
|
This won't work stable since refresh tokens change and it might work the first time but won't after a while or after restarting the backend pod after a token isn't active anymore. The best case would be to you optionally a RWX volume OR a secret that can be written via k8s API by the pod. I think the best option would be to use an RWX volume since most storage providers already provide that. |
Agreed. We need a feedback mechanism. |
It seems like I cannot go past the token generation, and I realized it is not just for GDrive but for all other backend types that requires token too like OneDrive, Mega and Box.
The text was updated successfully, but these errors were encountered: