Rclone config create automation for google drive

[zenjabba]

rclone config create doesn't allow for fully automated configuration (excluding the goole api auth which the user needs to log into the correct google drive account).

Currently this is what rclone currently presents with the following commandline

rclone config create sourcedrive drive --config=test-rclone.conf --drive-client-id=X --drive-client-secret=X

2018/10/12 04:30:52 NOTICE: Config file "test-rclone.conf" not found - using defaults Remote config If your browser doesn't open automatically go to the following link: http://127.0.0.1:53682/auth Log in and authorize rclone for access Waiting for code...

What I would like to see is with the following commandline

# rclone config create sourcedrive drive --config=test-rclone.conf --drive-client-id=X --drive-client-secret=X --headless-setup and it presents this following screen

go to the following link: https://accounts.google.com/o/oauth2/auth?access_type=offline&client_id=930690570454-ra711ct2peggpt0g98h09l56m0qt99td.apps.googleusercontent.com&redirect_uri=urn%3Aietf%3Awg%3Aoauth%3A2.0%3Aoob&response_type=code&scope=https%3A%2F%2Fwww.googleapis.com%2Fauth%2Fdrive&state=1c9a152ad22e7f5db484662e16130543
Log in and authorize rclone for access
Enter verification code>

[zenjabba]

Ok, I'm ready for this :)

[88lex]

Looking forward to this. Very useful when you get to it, thank you.

[InBrewJ]

You don't need to launch the interactive google api auth screen if you create a service account for google drive on the Google Cloud Platform - which is really useful for headless systems!

[zenjabba]

and that requests a user to configure a service account. I already have a rclone clientid and secret that I want to use. I'm dealing with dumb users.

[InBrewJ]

Fair enough! I've realised after struggling for a while (even with a service account) I can't get the command line config to work without firing up a web server for interactive auth with Google...

I'm running this (option 1):

rclone config create arupiot-auto drive \ --config=rclone.conf \ drive-client-id X \ drive-scope drive.readonly \ drive-service-account-file path_to_json

I've also tried this (option 2):

rclone config create arupiot-auto drive \ --drive-service-account-file= path_to_my_json \ --drive-client-id="" \ --drive-client-secret="" \ --drive-scope=drive.readonly \ --drive-root-folder-id=""

If I run rclone config interactively, it picks up my service account json file just fine and I don't need to do interactive auth. My use case needs a service account because we need permissions/integration with more GCP services.

When I run rclone config interactively to check the config values after running option 2 everything is empty. Spooky!

Thank you!

[InBrewJ]

I've just found the (probably) obvious workaround of using #!/usr/bin/expect -f

...it's not ideal

[zenjabba]

I'll wait till it's officially supported. I hate updating and debugging scripts more than I need too.