Re: [Duplicity-talk] Support for current Google Drive API?

[Norman Goldstein]

Thanks for the explanation.  I get the following error:

UnsupportedBackendScheme: scheme not supported in url: pydrive2://address@hidden/Backups/Duplicity

Here are the pydrive backends that I have (after applying the patch):

-rw-rw-r--. 1 root root 5167 May 31 14:26 pydrive2backend.py
-rw-rw-r--. 1 root root 4675 Mar 11 05:33 pydrivebackend.py
-rw-r--r--. 1 root root 5396 May 31 14:19 pydrivebackend.pyc

PS
As a test, I was also not successful in using plain pydrive.  I get the different error:

BackendException: GOOGLE_DRIVE_ACCOUNT_KEY environment variable not set.
Please read the manpage to fix.

When I create my google account id,
I am given the option of downloading either a json file or a key file, but not both.



On 05/30/2015 01:26 AM, Rupert Levene wrote:

You can use the pydrive backend instead of gdocs. pydrive uses storage
associated with a google service account which means you can't access
the backups using the Google Drive web interface or access any old
backups made using the gdocs backend, and your storage quota is
limited, but it does seem to work.

If you want to use the web-visible storage in your Google Drive user
account like the old gdocs backend, then you can patch the pydrive
backend - see my recent email to this list for instructions.

Rupert

On 30 May 2015 at 05:21, Norman Goldstein <address@hidden> wrote:

My duplicity logon to google-docs fails.  I am redirected to the web page

https://developers.google.com/identity/protocols/AuthForInstalledApps

which explains that

Important: ClientLogin has been officially deprecated since April 20, 2012
and
is now no longer available. Requests to ClientLogin will fail with a HTTP
404 response.
We encourage you to migrate to OAuth 2.0 as soon as possible.

The OAuth 2.0 web page is

https://developers.google.com/identity/protocols/OAuth2

which eventually leads to

https://developers.google.com/oauthplayground/

but this is where I lose the thread.
Has anyone figured this out?

Thank you.


[Please CC me on replies.]

The current Duplicity "gdocs" backend uses the deprecated "Google
Documents List Data API"
(https://developers.google.com/google-apps/documents-list/), which says:

Warning: The deprecation period for Version 3 of the Google Documents
List API is nearly at an end. On April 20, 2015, we will discontinue
service for this API. This means that service calls to the API are no
longer supported, and features implemented using this API will not
function after April 20, 2015. You must migrate to the Drive API as
soon as possible to avoid disruptions to your application.

Any plans to migrate to the Drive API?

Also, switching to the new API would avoid the need to supply a Google
username and password; instead, Duplicity could obtain an access token
with the appropriate permission (drive.file) to access only files
created with that token.

- Josh Triplett

_______________________________________________
Duplicity-talk mailing list
address@hidden
https://lists.nongnu.org/mailman/listinfo/duplicity-talk



_______________________________________________
Duplicity-talk mailing list
address@hidden
https://lists.nongnu.org/mailman/listinfo/duplicity-talk

_______________________________________________
Duplicity-talk mailing list
address@hidden
https://lists.nongnu.org/mailman/listinfo/duplicity-talk