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
[WIP] All Backends: add --backend-token flag - fixes #2849 #2852
[WIP] All Backends: add --backend-token flag - fixes #2849 #2852
Conversation
Sorry for the delay in replying to this! Christmas plus Norovirus has taken its toll! What you've written will work fine. I'm just wondering if it can or should be generalised. All the oauth based remotes could potentially do with this.
So we could extend your patch do do all of the backends like that? Or possibly be a bit more clever and reduce the code duplication a bit.... Maybe making an Likewise we should be able to do actually setting the token entirely in the oauthutil module I think. What do you think? |
Hey Nick, Happy New Year! No worries about the delay, I've been on holiday as well. I hope you are feeling better post-Norovirus 🤒. I agree with you that it would be nice to have this feature available regardless of the backend being utilized. I would be happy to take a crack at implementing; though i'm not 100% sure if I'd be able to test all the backends (I only currently have Dropbox + Google Drive creds). With regard to the current PR and failed Travis CI build, I'm having trouble understanding what the exact error is during the Thanks again, -Jake |
Thanks :-)
Great! The daily integration tests will run the backends against all the different providers so that will test that basic functionality isn't broken at least!
This is the relevant part of the log. What it means is that I'd like to make these code quality checks more obvious - I have a branch with gometalinter doing it which produces better error messages, but I couldn't get it to work with build tags.
|
Sorry for the loooong delay responding. Do you still want to work on this? I think the feature is a useful one, but only if we can make it for all backends that need it. |
@ncw I agree that this is an important feature, but unfortunately I won't be able to dedicate time to work on it in the near future. I think it would be best to hand this off to someone else. I'll go ahead and close the request. |
Thanks for your work on this - I'll pull it into a branch and have a think about how to continue it. |
Note: The scope of this PR now includes adding a similar
token
flag to each backend in Rclone. (In addition to the original Dropbox request.)What is the purpose of this change?
Add a
--dropbox-token
flag so that a user is able to supply an Access Token (as a JSON blob) outside of the defaultrclone.conf
file. Use of this option (in conjunction with --dropbox-client-idand --dropbox-client-secret) would allow users to to keep all plaintext credentials off-disk.
Was the change discussed in an issue or in the forum before?
No, just in the Github issue section. Please see #2849.
Checklist